Resolved after 1 hour 55 minutes, affecting APIs and Payment API v1 and 1 more, on November 6, 2026.
API response times have remained stable since 16:48 CET and this incident is now resolved. The latency was caused by a network degradation between our edge network provider and our cloud provider on traffic routed through Paris. No errors were observed and payment data integrity was not affected. We apologize for any inconvenience and keep monitoring.
Affected components
Update timeline
- investigating Nov 06, 2026, 03:53 PM UTC
Purse is experiencing a service degradation. We are observing latency degradation. We will update as we are able to remediate. More updates to follow shortly
- investigating Nov 06, 2026, 04:09 PM UTC
Between 15:35 and 16:20 CET today, API calls to Purse experienced elevated response times, with some requests taking several seconds. A shorter recurrence occurred between 16:42 and 16:48 CET. Response times have since returned to normal. The cause has been identified as a network degradation between our edge network provider and our cloud provider, affecting traffic routed through Paris. Our platform itself remained healthy: no elevated error rate was observed, and requests completed successfully with higher latency. Payment data integrity was not affected. We are monitoring the situation closely and are in contact with the providers involved. We will post an update if the degradation recurs.
- resolved Nov 06, 2026, 04:30 PM UTC
API response times have remained stable since 16:48 CET and this incident is now resolved. The latency was caused by a network degradation between our edge network provider and our cloud provider on traffic routed through Paris. No errors were observed and payment data integrity was not affected. We apologize for any inconvenience and keep monitoring.
Your product runs on more than Purse
Add the vendors you depend on and get one message when any of them reports trouble. Free for 3 vendors, no card.
Amazon Web Services