Pegasus Platform API Access Interruption

Update timeline

1. investigating May 06, 2026, 06:06 PM UTC

   You may notice an interruption in the Pegasus application due an internal system error with the APIs, our team is actively working to resolve the interruption.

2. investigating May 06, 2026, 06:25 PM UTC

   Thanks for your patience. The team continues to actively work to resolve the issue. We've identified potential sources of the interruption and taking a deep dive at the affected servers.

3. identified May 06, 2026, 07:01 PM UTC

   We have identified the source of the problem and are working to try and resolve it without causing further negative implications.

4. identified May 06, 2026, 07:41 PM UTC

   The team continues working to try and recover the service; we're being careful not to cause any data loss or misfires

5. identified May 06, 2026, 08:26 PM UTC

   We continue working on finding the resolution to this error and appreciate your patience during this. It's affecting specific API endpoints that rely on an internal cache that's unavailable.

6. identified May 06, 2026, 09:03 PM UTC

   We are seeing signs of improvement in our testing environment after applying recovery actions. The team remains fully focused on validating system behavior

7. identified May 06, 2026, 09:34 PM UTC

   We are observing continued improvement after validating a patch in our testing environment. Recovery actions are being applied gradually across affected sites, and we are closely monitoring system behavior while we continue validating stability before considering this incident fully resolved.

8. identified May 06, 2026, 11:34 PM UTC

   Recovery actions are continuing across affected services, and message queues are being closely monitored as functionality is restored gradually. We continue validating system behavior before considering this incident fully resolved.

9. identified May 07, 2026, 01:33 AM UTC

   We continue working on service restoration across affected sites. We have made progress on recovery actions and are seeing improvements in system responsiveness. Ongoing monitoring will guide our next steps toward full resolution.

10. identified May 07, 2026, 02:48 AM UTC

    We've restored most critical services and are looking at restoring an important part of the vehicles API endpoint related to their properties. we'll continue to update as we make progress.

11. monitoring May 07, 2026, 05:32 AM UTC

    All core functionalities are restored; we're continuing to monitor the queues to ensure that the system is fully operational. If you are having troubles with API integrations then it's recommended to update or rotate the token for your application. Reach out to our [email protected] team while we work on a root cause analysis.

12. monitoring May 07, 2026, 05:47 AM UTC

    Services restored. Monitoring will resume throughout the night and into the morning while the activity picks back up again. Thank you for your patience throughout this incident. We will have a root cause analysis of everything soon.

13. monitoring May 07, 2026, 08:08 AM UTC

    We're continuing to monitor the services and ensuring that the system stays operational during the ramp up to the peak traffic. Please reach out to [email protected] if you have any questions.

14. identified May 07, 2026, 12:42 PM UTC

    Our team continues to work on resolving the issues experienced with the platform. Once all services are fully stabilized, we will provide a comprehensive incident report . In the meantime, please feel free to contact our support team via your designated support channel or email to report any ongoing issues.

15. identified May 07, 2026, 01:54 PM UTC

    Monitoring continues as we validate service behavior and platform performance. Recovery progress has been maintained, and we are closely reviewing key components to ensure stable operation.

16. identified May 07, 2026, 03:47 PM UTC

    We continue making progress on recovery. The team is actively working through the remaining steps and validating service behavior across sites. We'll keep updating as we move forward.

17. identified May 07, 2026, 04:56 PM UTC

    We continue working through the remaining components of our recovery plan. Several affected sites are now operational, and we are systematically validating service stability across all remaining components. The team remains focused on completing the full restoration.

18. identified May 07, 2026, 06:02 PM UTC

    Geofence and vehicle properties have been restored across affected sites. Asset properties are being progressively restored as the team continues working through the remaining components. We appreciate your continued patience.