Sematext Outage History

Sematext is up right now

Pingoru has recorded 5 incidents for Sematext: 5 in the last 12 months and 1 in the last 90 days.

Source: status.sematext.com

5incidents recorded
5last 12 months
1last 90 days
42 hourstypical duration
Incidents per month
024AprMayJunJulAugSepOctNov0
Share of hours with an open incident, any severity
0%50%100%AprMayJunJulAugSepOctNov0%
Pingoru began tracking Sematext in April 2026, so earlier months are not shown. Hover a bar for its value.
Show as a table
MonthIncidentsHours with an open incident
April 202600 of 720 (0%)
May 2026297 of 744 (13%)
June 2026059 of 720 (8%)
July 202600 of 744 (0%)
August 2026355 of 744 (7%)
September 202600 of 720 (0%)
October 202600 of 744 (0%)
November 202600 of 137 (0%)

Incidents, newest first

Minor August 18, 2026 Data ingestion delay 1h 10m

Started Aug 18, 2026, 12:03 PM UTC· resolved Aug 18, 2026, 01:14 PM UTC

  1. investigating Aug 18, 2026, 12:05 PM UTC

    Some customers may experience seeing logs, metrics, traces, or other data with some delay. We are working on the issue.

  2. resolved Aug 18, 2026, 01:14 PM UTC

    Ingestion is back to normal and data is flowing into Sematext without delays.

Read the full incident report →

Minor August 7, 2026 Increased Latency in Synthetics Runs 1d 13h

Started Aug 07, 2026, 06:00 PM UTC· resolved Aug 09, 2026, 07:24 AM UTC

  1. investigating Aug 08, 2026, 01:17 PM UTC

    We are currently investigating reports of increased latency affecting Synthetics runs among several Synthetics apps in US region. Our engineering team is actively working to identify the root cause and restore normal performance as quickly as possible. We will share the next update as soon as more information becomes available. Thank you for your patience!

  2. resolved Aug 09, 2026, 07:24 AM UTC

    We dealt with latency in all Synthetics apps. Sorry for the inconvenience caused and thank you for your understanding!

Read the full incident report →

Minor August 3, 2026 Logs delay 16h

Started Aug 03, 2026, 03:00 PM UTC· resolved Aug 04, 2026, 07:01 AM UTC

  1. investigating Aug 03, 2026, 02:58 PM UTC

    Some customers may experience significant latency when viewing recent logs, or a temporary pause in new logs appearing in their dashboards. Our engineering team is actively investigating the root cause regarding log ingestion pipeline. We apologize for any inconvenience and will provide a final update once latency has completely vanquished.

  2. resolved Aug 04, 2026, 07:01 AM UTC

    Logs pipeline issues resolved. Thank you for your understanding and apologize for the inconvenience caused!

Read the full incident report →

Minor May 28, 2026 Scheduled infrastructure maintenance 6d 3h

Started May 28, 2026, 07:00 AM UTC· resolved Jun 03, 2026, 10:41 AM UTC

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

    A scheduled infrastructure upgrade will happen. The application may become unavailable for a brief duration of time.

  2. resolved Jun 03, 2026, 10:41 AM UTC

    Infrastructure maintenance completed.

Read the full incident report →

Minor May 5, 2026 Log ingestion delay 7h 55m

Started May 05, 2026, 10:46 AM UTC· resolved May 05, 2026, 06:42 PM UTC

  1. investigating May 05, 2026, 10:48 AM UTC

    We are experiencing an increased latency in ingestion of logs. We have identified the root cause and working on a fix.

  2. resolved May 05, 2026, 06:42 PM UTC

    This problem has been resolved.

Read the full incident report →