SumUpIssue with Logins and Payments Acceptance
The issue has been fixed. SumUp services have returned to normal. You can stay up to date on the status of our services anytime here on our status page: https://status.sumup.com.
Resolved
Outages and recoveries from the services you depend on.
40 incidents
The issue has been fixed. SumUp services have returned to normal. You can stay up to date on the status of our services anytime here on our status page: https://status.sumup.com.
Resolved
From 21:00 on Aug 16 to 01:50 on Aug 17 UTC, some Bancontact payments experienced elevated processing errors. This issue has now been resolved.
Resolved
This incident has been resolved.
Resolved
We have identified this as a non-user impacting alert and as such this is being resolved.
Resolved
This incident has been resolved.
Resolved
The issue affecting claude.ai, platform.claude.com, the Claude API, Claude Code, and Claude Cowork has been resolved.
Resolved
Microsoft's Outlook team has confirmed that mitigations have been implemented. We've verified that email delivery to Microsoft 365 domains is operating normally again. This incident has been resolved.
Resolved
The server has remained stable since the fix was implemented. The issue is resolved at this time. If you do have any questions please do not hesitate to reach out to our Support team.
Resolved
The health issue with Navy Federal Credit Union has been resolved
Resolved
Granola services should now be up and running again - let us know at hey@granola.so "hey@granola.so": mailto:hey@granola.so if you're still having issues. Any notes that you took during the outage should be safe - you may need to hit retry on any notes to generate them fully. We're really sorry for any disruption.
Resolved
We've resolved the incident and the affected service is now operational.
Resolved
We've resolved the incident and the affected service is now operational.
Resolved
We've resolved the incident and the affected service is now operational.
Resolved
We've resolved the incident and the affected service is now operational.
Resolved
All post-outage cleanup activities have been completed, and everything is working as expected. We will continue to monitor the environment, and this incident is now resolved.
Resolved
This incident has been resolved.
Resolved
We've resolved the incident and the affected service is now operational.
Resolved
Between 19:54 and 20:07 UTC on August 15, requests to our US error reporting API (api.honeybadger.io) experienced an elevated failure rate. During this window, a majority of requests to submit errors and events timed out or received 5xx responses. Browser (JavaScript) error reporting, source map uploads, the Honeybadger web application, dashboards, uptime monitoring, and our EU region were not affected. What happened: Beginning at 19:54 UTC, a single source began submitting error reports at roughly 150 times its normal rate, with payloads several times larger than average. This more than doubled the total volume of data arriving at our ingestion tier, which saturated within a minute. Because the saturated service kept accepting connections rather than returning errors outright, our autoscaling and alerting — which watch for error responses — did not register the problem quickly, and capacity was added later than it should have been. Service recovered at 20:07 UTC once additional capacity came online. Most affected reports were retried successfully by our client libraries once the API recovered, so the large majority of data submitted during the window was ultimately received. Reports sent by libraries without retry logic were not received and cannot be recovered. What we've done: our ingestion tier now scales on response latency in addition to error rates, so this kind of saturation is detected within a minute or two rather than only once errors appear. We've also raised the tier's baseline capacity and widened our paging alerts to cover failures that don't surface as server errors. We're additionally adding limits on how much data a single source can submit. We're sorry for the disruption, and for any gaps this caused in your error data during the window.
Resolved
This incident has been resolved.
Resolved
We incurred a temporary delay on the legacy ingestion path for v4. This delay has been resolved. OTEL ingestion has not been impacted.
Resolved
We had an incident on Storage offer which has now been resolved. Here are some supplementary details : <b>Start time :</b> 15/08/2026 13:25 UTC <b>End time :</b> 15/08/2026 14:10 UTC <b>Impacted Service(s) :</b> The Block Storage service is experiencing latency for some customers in the GRA3 region. <b>Customers Impact :</b> Customers may have temporarily experienced latency affecting their Block Storage services in the GRA3 region. <b>Root Cause :</b> A service disruption occurred due to an unexpected underlying infrastructure malfunction. We thank you for your understanding and patience throughout this incident.
Resolved
Following planned maintenance that ended at 13:00 UTC on August 15, some impact to job processing continued for approximately 30 minutes beyond the window we announced. Some customers continued to see delays in jobs starting, along with a small number of jobs failing with infrastructure errors, until approximately 13:30 UTC. This has been resolved and job processing has returned to normal. Customers whose jobs failed during this window may rerun affected jobs. We thank you for your patience while our team worked on implementing a fix and apologize for any inconvenience the extended impact may have caused.
Resolved
Between 04:01 and 05:42 UTC, we saw elevated error rates and response times with Mastercard payments. This is now resolved. Our engineering teams will continue to monitor.
Resolved
Card payment processing has returned to normal. The earlier issue with Mastercard and Maestro payments was caused by a third-party network problem and has been fixed. Please retry any payments that failed during the incident. We apologise for the inconvenience.
Resolved
Mastercard Network Outage has been resolved, and transactions should now be correctly processed.
Resolved
We are pleased to inform you that the incident affecting our File storage offering has been resolved. <b>Start time :</b> 14/08/2026 14:43 UTC <b>End time :</b> 15/08/2026 05:25 UTC <b>Root Cause :</b> A service disruption occurred due to an unexpected infrastructure failure. We apologize for any inconvenience caused and appreciate your understanding.
Resolved
We are pleased to inform you that the incident affecting our Compute - Instance offering has been resolved. <b>Start time :</b> 14/08/2026 14:43 UTC <b>End time :</b> 15/08/2026 05:25 UTC <b>Root Cause :</b> A service disruption occurred due to an unexpected infrastructure failure. We apologize for any inconvenience caused and appreciate your understanding.
Resolved
The issue affecting Claude services has been resolved. Impact occurred from 20:00 Aug 14, 2026 to 00:11 Aug 15 , 2026 UTC.
Resolved
This issue has been resolved and service is operating normally. A post-incident review will be conducted.
Resolved
This incident has been resolved. Email delivery was delayed between 15:45 EDT and 16:35 EDT due to an issue with an upstream email service provider. This affected customers who have not yet configured a custom email domain or a custom email provider.
Resolved
The issue affecting the Claude API, Claude Code, and Claude Cowork has been resolved. Impact occurred from 20:14 to 20:38 UTC.
Resolved
We've resolved the incident and the affected service is now operational.
Resolved
We've resolved the incident and the affected service is now operational.
Resolved
This issue is now resolved.
Resolved
We've resolved the incident and the affected service is now operational.
Resolved
This incident has been resolved.
Resolved
We've resolved the incident and the affected service is now operational.
Resolved
This issue has been resolved. Connectivity has returned to normal.
Resolved
We can confirm that the issue was mitigated at 14:48 UTC on August 14, 2026, and the service has resumed normal operation. Customers and partners can view additional details about the incident by logging in to: https://community.akamai.com/customers/s/feed/0D5a700001NmwELCAZ or reaching out to Akamai Support. We apologize for the impact and thank you for your patience and continued support. We are committed to making continuous improvements to make our systems better and prevent a recurrence of this issue.
Resolved
Fix deployed to server, `eas-cli@22.0.0` set back to `latest`.
Resolved