Social Champ, Inc Outage History
5 incidents recorded over the last 365 days, 5 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.
Every Recorded Social Champ, Inc Incident
| Date | Incident | Duration | Status |
|---|---|---|---|
| Jul 19, 2026 | Issue Publishing Posts to Instagram and Threads | 1765h 57m | Resolved |
| Jul 3, 2026 | Intermittent Publishing Failures on X (Twitter) | 2150h 43m | Resolved |
| Jun 23, 2026 | LinkedIn API Outage | 1665h 21m | Resolved |
| Jun 12, 2026 | Meta API disruption | 1929h 24m | Resolved |
| Jun 1, 2026 | Calendar Glitch | 2199h 37m | Resolved |
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 Social Champ, Inc 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 Social Champ, Inc 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 Social Champ, Inc 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 Social Champ, Inc outage in this window ran 91d 15h, against a mean recovery of 80d 22h. If you depend on Social Champ, Inc 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.