Over after 3 min18 Oct
Check failures in the Amsterdam group
20 services stopped answering in 1 monitoring group for 3 min, from 22:28 to 22:30.
Failing, minute by minute
100
22:2822:30
Monitoring-group history
- Amsterdam22:28
What the status pages said
- Twilio's status page already showed it.“SMS Delivery Failures from Twilio Alphanumeric Sender IDs to Multiple Networks in Turkey”
- Clerk's status page already showed it.“Development instances only - Apple rejecting emails”
- MongoDB Atlas admitted it 3 min after it began failing.“Impaired Cluster operations in AWS me-central-1 and AWS me-south-1”
- Fastly said nothing.
- bunny.net said nothing.
- PayPal said nothing.
- Supabase said nothing.
- DeepSeek said nothing.
- Akamai Cloud (Linode) said nothing.
- Hugging Face said nothing.
- Cursor said nothing.
- Resend said nothing.
- Stripe said nothing.
What it took down
Services
- FastlyAMS22:29–22:30
- bunny.netAMS22:29–22:30
- WhatsAppAMS22:29–22:30
- PayPalAMS22:29–22:30
- SpotifyAMS22:29–22:30
- SupabaseAMS22:30–22:30
- MongoDB AtlasAMS22:30–22:30
- jsDelivrAMS22:30–22:30
- SalesforceAMS22:30–22:30
- ClerkAMS22:30–22:30
- DeepSeekAMS22:28–22:30
- Akamai Cloud (Linode)AMS22:29–22:30
- Oracle CloudAMS22:29–22:30
- Hugging FaceAMS22:28–22:29
- CursorAMS22:28–22:29
- TwilioAMS22:28–22:29
- ResendAMS22:28–22:29
- StripeAMS22:28–22:29
- BinanceAMS22:28–22:29
- X (Twitter)AMS22:28–22:29
Timeline
- 22:24Twilio's status page admitted it
- 22:28It began: Amsterdam
- 22:29Clerk's status page admitted it
- 22:30It was over
- 22:33MongoDB Atlas's status page admitted it