pingoru pingoru Memfault had 8 outages in the last 2 years totaling 15h 17m of downtime, averaging 0.3 incidents per month.
There were 8 Memfault outages since October 24, 2024 totaling 15h 17m of downtime. Each is summarised below. Incident details, duration, and resolution information.
We are aware of an issue preventing new devices from appearing in device search. We are currently implementing a fix for this and expect to restore functionality later today. No devices or data have been lost.
This incident has been resolved.
Our upstream DNS provider is having an incident. Some services may be unavailable. We are monitoring and will report once the issue has been resolved.
The upstream DNS provider is recovering from the incident and our services have become accessible again via their respective domain names. We will keep monitoring until the upstream DNS provider communicates this incident is fully resolved.
Our data processing infrastructure is running behind. No data has been lost and the system should be caught up shortly.
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
We're seeing elevated chunks-ingress errors (chunks.memfault.com), related to today's large AWS outage. We're investigating.
The issues with chunks ingress have been resolved. The API is no longer returning errors and should be behaving normally.
An AWS operational issue in us-east-1 affected multiple services. Restoration of service is now underway and we are seeing traffic flow in again. We expect some ingestion backlogs and additional latency as everything returns to normal. We are monitoring and will provide updates as needed.
We are continuing to monitor for any further issues.
This incident has been resolved.
We are currently investigating this issue.
A fix has been implemented and we are monitoring the results.
We are continuing to monitor for any further issues.
This incident has been resolved; all systems are fully operational.
Memfault experienced a briefly elevated level of API errors. Users may have seen errors between 15:50 UTC and 16:12 UTC. The issue is now resolved.
We are currently experiencing a small delay in data ingestion and some charts may be slow to load for some customers. We are actively working on a fix and will post an update as soon as it is deployed.
The issue has been identified and a fix is being implemented.
The data ingestion delay is recovered and chart query performance has returned to normal response times. We are continuing to monitor system performance and will post any further updates.