MachineMetrics Outage History

29 incidents recorded over the last 365 days, 22 of them resolved. Durations are measured from when PulsAPI first saw the problem to when it cleared, which is usually longer than the vendor's own figure.

Live MachineMetrics status100.00% uptime history

Every Recorded MachineMetrics Incident

MachineMetrics incidents, newest first, with date, duration and status.
DateIncidentDurationStatus
Oct 30, 2026Machine Data Processing Delayed for Some SystemsThis incident has been resolved2h 6mResolved
Oct 21, 2026Elevated Query Response TimesResponse times have returned to within the normal range at this time50 minResolved
Oct 6, 2026Labor Ticket Form OutageThere was an issue with displaying the Submit Work form for MES enabled customers. The incident has been resolved.-18437 minResolved
Sep 27, 2026Backend UpgradesThe scheduled maintenance has been completed.1h 0mScheduled
Aug 19, 2026Shift Based Reporting InaccurateThis incident has been resolved.2h 20mResolved
Aug 12, 2026Machine Data Ingest LaggingThis incident has been resolved. All machine data has been processed.3h 15mResolved
Aug 9, 2026Backend System MaintenanceThe scheduled maintenance has been completed.2h 0mScheduled
Jul 26, 2026Machine Data Processing Delayed for Some SystemsThis incident has been resolved.1h 49mResolved
Jul 15, 2026Machine Data Processing Delayed for Some SystemsThis incident has been resolved.1h 3mResolved
Jul 12, 2026Backend Infrastructure MaintenanceThe scheduled maintenance has been completed.2h 0mScheduled
Jul 10, 2026Historical Reporting Delayed, InvestigatingThis incident has been resolved.26 minResolved
Jun 18, 2026Some Web Pages FailingThe fix has been deployed to all production environments and pages should be loading normally now. A page reload may be required for the fix to apply in some cases.57 minResolved
Jun 9, 2026Historical Reporting is BehindThis incident has been resolved.4h 44mResolved
Jun 7, 2026Backend UpgradesThe scheduled maintenance has been completed.1h 0mScheduled
Jun 4, 2026Data Ingest Lagging and Higer Response TimesThis incident has been resolved.22 minResolved
Jun 2, 2026Increased Error RateThis incident has been resolved.8 minResolved
Jun 2, 2026Intermittent Errors and Degraded PerformanceThe incident is resolved at this time.26 minResolved
May 31, 2026Backend UpgradesThe scheduled maintenance has been completed.2h 0mScheduled
May 28, 2026Central Querying System DownThis incident has been resolved.20 minResolved
May 20, 2026App and ShopPulse Response Times SlowApplication performance has improved to acceptable levels. While we are closing this incident, we will continue to make improvements to application performance and stability.3h 47mResolved
May 4, 2026Machine Data Not Reporting for Some CompaniesAll data is reporting normally.10h 53mResolved
Apr 19, 2026Backend Infrastructure MaintenanceThe scheduled maintenance has been completed.1h 0mScheduled
Apr 1, 2026Categorized Downtime in Historical Reporting LaggingThis incident has been resolved.2h 56mResolved
Mar 31, 2026Historical Reporting LaggingThis incident has been resolved.2h 13mResolved
Mar 18, 2026System OutageThis incident has been resolved.5 minResolved
Feb 25, 2026Data Processing LagData processing is operating as expected for the impacted services.2h 44mResolved
Feb 23, 2026Infrastructure MaintenanceThe scheduled maintenance has been completed.2h 0mScheduled
Jan 28, 2026Increased Error RateThis incident has been resolved.2h 44mResolved
Jan 22, 2026Data Ingest LaggingThis incident has been resolved.10 minResolved

Hear about the next one while it is open

Everything above is a record written after the fact. We can email you when the next MachineMetrics incident opens instead, at the point where knowing still changes what you do.

Free, no password, no card. Unsubscribe in one click.

How to Read This MachineMetrics Incident Log

Each row is an incident PulsAPI observed, not a summary written afterwards. The duration is wall-clock time between the first failing check and the first clean one, so it includes the window before MachineMetrics acknowledged anything. Vendor post-mortems typically measure from acknowledgement, which is why their numbers are usually shorter.

Incidents still open have no duration yet and are listed as ongoing rather than being given a running total. The archive covers the last 365 days; anything older has aged out of the window rather than never having happened.

The longest single MachineMetrics outage in this window ran 10h 53m, against a mean recovery of 1h 59m. If you depend on MachineMetrics in a customer-facing path, the longest figure is the one to design around. The mean is what happens on a normal bad day; the maximum is what happens on the worst one.