Maxio incident

Brief Service Disruption – February 17, 2025

Resolved on February 17, 2025.

resolved Feb 17, 2025, 07:02 PM UTC

Incident Summary: On February 17, 2025, from 10:31:57 AM to 10:32:13 AM EST, A system change caused an unexpected service disruption of 16 seconds. During this time, some users experienced temporary unavailability via the API and UI, with a limited number of lost connections. Resolution: The issue was quickly identified and resolved. The system is now fully operational. Next Steps: Customers who encountered a 500 error during this period should retry their API requests. We are reviewing our processes to prevent similar occurrences in the future.

Started
Feb 17, 2025, 03:30 PM UTC
Resolved
Feb 17, 2025, 03:30 PM UTC
Duration
–
Detected by Pingoru
Feb 17, 2025, 03:30 PM UTC

Update timeline

  1. resolved Feb 17, 2025, 07:02 PM UTC

    Incident Summary: On February 17, 2025, from 10:31:57 AM to 10:32:13 AM EST, A system change caused an unexpected service disruption of 16 seconds. During this time, some users experienced temporary unavailability via the API and UI, with a limited number of lost connections. Resolution: The issue was quickly identified and resolved. The system is now fully operational. Next Steps: Customers who encountered a 500 error during this period should retry their API requests. We are reviewing our processes to prevent similar occurrences in the future.

Your product runs on more than Maxio

Add the vendors you depend on and get one message when any of them reports trouble. Free for 3 vendors, no card.

Add your stack →