Salla Platform Outage History
3 incidents recorded over the last 365 days, 1 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 Salla Platform Incident
| Date | Incident | Duration | Status |
|---|---|---|---|
| Oct 28, 2026 | صيانة مجدولة - 28 اكتوبر 2026 | Scheduled Maintenance – October 28, 2026Scheduled Maintenance | 5h 0m | Scheduled |
| Oct 9, 2026 | صيانة مجدولة - 09 اكتوبر 2026 | Scheduled Maintenance – October 9, 2026 | December 23, 2025Scheduled Maintenance | 6h 0m | Scheduled |
| Aug 20, 2026 | تحديث حالة إشعارات تطبيقات التجار | 13h 53m | 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 Salla Platform 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 Salla Platform 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 Salla Platform 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 Salla Platform outage in this window ran 13h 53m, against a mean recovery of 8h 18m. If you depend on Salla Platform 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.