Is Digital Communications Technologies down?
Last checked just nowNo incidents right now.
Digital Communications Technologies is operational right now. Last checked just now; the most recent incident resolved 23d ago.
Real-time Digital Communications Technologies status, recent outages, and incident history — pulled directly from Digital Communications Technologies's official status page at https://status.digitalcomtech.com every 5 minutes. Pingoru tracks 22 Digital Communications Technologies services and has captured 3 incidents in the last 90 days (99.44% uptime). Get email, Slack, Discord, or webhook alerts the moment Digital Communications Technologies reports a new incident — free for 5 monitors, no credit card.
Recent outages & incidents
Past 90 days- Connectivity - SuperSIM Connectivity
Timeline · 1 update
- investigating · May 21, 2026, 04:06 PM UTC
Who Impacted Customer Solutions: Super SIM Impacted Services: Network Registration When Start: Thursday, May 21, 2026, 11:27 UTC / Thursday, May 21, 2026, 08:27 EDT (UTC-4) End: TBD What Description: Since approximately 11:27 our systems have detected an increase in devices reattaching to the network using the Super SIM US products. Devices are receiving a higher than expected rate of failures to attach. The issue is only with establishing new data sessions. Established data sessions are not impacted. Engineers are actively working to resolve the issue. We will update as more information becomes available. UPDATE 1 2026-05-21 15:09 UTC / 11:09 EDT (UTC-4): We are currently experiencing Super SIM connectivity issues where approximately 25% of data sessions are impacted. Our engineering team is actively working to resolve the issue. For further assistance contact: [email protected]
Latest: Who Impacted Customer Solutions: Super SIM Impacted Services: Network Registration When Start: Thursday, May 21, 2026, 11:27 UTC / Thursday, May 21, 2026, 08:27 EDT (UTC-4) End: TB…
-
- APIAWS Data Center
Timeline · 22 updates
- 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.
- 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.
- 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.
- 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
- 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.
- 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
- 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.
- 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.
- 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.
- 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.
- 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.
- 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.
- 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.
- 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.
- 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.
- 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.
- 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.
- 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.
- identified · May 07, 2026, 07:04 PM UTC
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.
- identified · May 07, 2026, 08:03 PM UTC
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.
- identified · May 07, 2026, 09:03 PM UTC
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.
- monitoring · May 07, 2026, 10:13 PM UTC
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.
Latest: 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.
-
- Started May 21, 2026, 04:06 PM UTC · Resolved May 21, 2026, 09:03 PM UTC · 4h 56m
- Started May 06, 2026, 06:06 PM UTC · Resolved May 11, 2026, 01:07 PM UTC · 4d 19h