Can you share the ray IDs with me? They're safe to put in public
Can you share the ray IDs with me? They're safe to put in public
Mof course,
858715f22c0b0e48-AMS and 858715f22c0f0e48-AMS. If it helps: location hint on the bucket at creation time was Western Europe, and our requests should've come from NL
EThanks
MI do see a CF incident on R2 just now (13:48Z), both requests were done some 20 minutes before (13:27Z). I also have a few requests around that same timestamp that completed <200ms, ray ID's available ifneedbe.
EFrom what I can understand it likely would be best to wait until the incident is resolved and if its still happening at that point then I can dig further
EThe statuspage is updated manually, there is often times where impact is present or ramping up for a time before we noticed and went through the motions of updating it
MYeah, I figured that as well.
MThanks, I'll keep that in mind and collect Ray ID's when it happens again.
GSame issue, we've been facing it for a good 2-3hrs before the incident was acknowledged and are still experiencing the problem
GTotal of 5 hours since it started
GNo idea. A full 2hours before they acknowledged the incident we opened a support ticket providing 10 ray IDs with high R2 latency and even narrowed down the problem to the 2 EU regions. A large % of our requests faced this, unless we were hit unusually hard compared to others, it's difficult to imagine the impact being so low during that time that it doesn't warrant a status page update
ZI got a huge spike of HTTP 500 errors here
ZWEUR bucket
GInterestingly, we didn't get a single 500, only requests always taking a little over 15 seconds. As if an internal service is timing out after that time, but somehow not causing an error?
GHonestly 500s would be better, this way our users are waiting for a loading spinner for 30 seconds because we do 2 R2 writes on the backend... not fun
EWhat is the ticket num?
EIt was probably retried internally but 15 seconds is way too long to be acceptable even in error
G3153662
EThanks
OYup, still seeing some requests take a long time. Not as many as 2 hours ago though.
EI looked into these further and my understanding is that they are related to the incident, I'm not sure why some saw impact start much earlier however
SGetting 500 a lot on trying to upload with a signed URL, i'm having to retry my requests up to 10 times
SSEastern Europe (EEUR)
C
Swell that would explain it
Useems its probably resolved to me :NODDER:
Uminimal issues in the last hour
Uguess theres still the occasional high latency request but not really any errors
EI've added
We have deployed some further fixes and are seeing improvements. We are continuing to monitor for any further issues.
Lhow to protect videos url from other site?
Lhow can i get free?
Li don't know coding
UYou cant protect videos from another site realistically there will always be ways around it
UYou dont need to know how to code to setup CORs though you just set what the url to your site is pretty much
ENow marked resolved
Lhow can you guide me?
UE@mrngm @geomaster @Ohyzd @Scruffy are you still seeing issues? We've closed out the incident as resolved
Lprotect mean off the urls hotlinking to other site
S225af28a5aa74bd199db63641e9b1efd
GStill seeing high latencies, also errors this time
ECan you reply to the ticket with more information so I can take a look?
OYes, 2nd GET request I've tried - 85885d542a6d5b18-VIE - just over 15 seconds. The ~20 I tried afterwards finished in 150-500ms though.
GWhich information do you need?
Gray IDs?
HIs there any way I can view my bucket as a Directory listing?
Chey, I need to clear all failed uploads that still show how can I do this?
