Active Incident

Updated a few seconds ago

Pegasus Platform API Access InterruptionOperational

Incident Status

Operational

Components

API

Locations

AWS Data Center


May 7, 2026 6:13PM EDT
MONITORING

Services are now stable and operating. We are continuing to monitor closely to ensure sustained performance. Thank you for your patience while we worked through this incident.

May 7, 2026 5:03PM EDT
IDENTIFIED

We’ve made additional progress on token restoration, and recovery work continues across the remaining functionality. We are validating each step and will share another update as soon as the next set of improvements is confirmed.

May 7, 2026 4:03PM EDT
IDENTIFIED

Some features are still being restored, and we are validating each step as work continues. We’ll share another update as soon as we confirm the next set of improvements.

May 7, 2026 3:04PM EDT
IDENTIFIED

Recovery actions are continuing across affected sites. Most components have been successfully restored, and the team is working through the remaining items. We will continue to update as we make further progress.

May 7, 2026 2:02PM EDT
IDENTIFIED

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.

May 7, 2026 12:56PM EDT
IDENTIFIED

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.

May 7, 2026 11:47AM EDT
IDENTIFIED

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.

May 7, 2026 9:54AM EDT
IDENTIFIED

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.

May 7, 2026 8:42AM EDT
IDENTIFIED

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.

May 7, 2026 4:08AM EDT
MONITORING

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 support@digitalcomtech.com if you have any questions.

May 7, 2026 1:47AM EDT
MONITORING

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.

May 7, 2026 1:32AM EDT
MONITORING

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 support@digitalcomtech.com team while we work on a root cause analysis.

May 6, 2026 10:48PM EDT
IDENTIFIED

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.

May 6, 2026 9:33PM EDT
IDENTIFIED

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.

May 6, 2026 7:34PM EDT
IDENTIFIED

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.

May 6, 2026 5:34PM EDT
IDENTIFIED

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.

May 6, 2026 5:03PM EDT
IDENTIFIED

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

May 6, 2026 4:26PM EDT
IDENTIFIED

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.

May 6, 2026 3:41PM EDT
IDENTIFIED

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

May 6, 2026 3:01PM EDT
IDENTIFIED

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

May 6, 2026 2:25PM EDT
INVESTIGATING

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.

May 6, 2026 2:06PM EDT
INVESTIGATING

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.

API

Operational

Application

Operational

Connectivity - Super

Operational

Connectivity - Wireless

Operational

Dashboards

Operational

Forwarders

Operational

Listeners

Operational

Live

Operational

Notifications

Operational

Triggers

Operational

Reports

Operational

0

Upcoming Maintenances

1

Incidents Last 30 Days

1

Maintenances Last 30 Days

External Services

Amazon Web Services

AWS CloudFront

AWS EC2

DigitalOcean

GitHub

Google Cloud

Slack

SoftLayer

History (Last 7 days)

Scheduled Maintenance - Monday May 4, 2026 01:00 UTCPlanned Maintenance

Description

Scheduled Maintenance Notification Start date: Monday May 04, 2026 01:00 UTC End date: Monday May 04, 2026 05:00 UTC Duration: 4 Hours Type: Maintenance Impact: Web access and listeners interruptions Descripción: Engineering team will perform a data base update | At some point during the 4 hours window time, there will be access and listeners interruptions for 15 minutes | All sites impacted. For further information please check our status page: https://status.digitalcomtech.com/ Mantenimiento Notificación de mantenimiento programado Fecha de inicio: Lunes 4 - Mayo - 2026 01:00 UTC Fecha de finalización: Lunes 4 - Mayo - 2026 05:00 UTC Duración: 4 Horas Tipo: Mantenimiento Impacto: Interrupción en acceso web y listeners Descripción: Se realizará una actualización en la base de datos, se presentará interrupción en el acceso web y los listeners por 15 Minutos en cualquier momento durante la ventana de mantenimiento Sitios Asociados al mantenimiento: Todos los sitios


Components

Listeners


Locations

AWS Data Center


Schedule

May 3, 2026 9:00PM - May 4, 2026 1:00AM EDT


May 4, 2026 1:00AM EDT
UPDATE

Scheduled maintenance finished. | Finalizando mantenimiento programado.

May 3, 2026 9:00PM EDT
UPDATE

Scheduled maintenance starting.... | Iniciando mantenimiento programado...