Semji Outage History

6 incidents recorded over the last 365 days, 6 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 Semji status99.43% uptime history

Every Recorded Semji Incident

Semji incidents, newest first, with date, duration and status.
DateIncidentDurationStatus
Oct 30, 2026SEO analyses temporarily unavailable141h 53mResolved
Oct 28, 2026Database maintenance3h 0mResolved
Oct 21, 2026Security Update – Recent PHP Vulnerabilities2h 20mResolved
Sep 3, 2026ChatGPT GEO analyses temporarily unavailable1502h 45mResolved
Jul 28, 2026Analysis are down due to external services1549h 46mResolved
Jun 23, 2026Service Degradation Notice1665h 25mResolved

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 Semji 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 Semji 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 Semji 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 Semji outage in this window ran 69d 9h, against a mean recovery of 33d 18h. If you depend on Semji 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.