InterExchange Outage History

22 incidents recorded over the last 365 days, 18 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 InterExchange status100.00% uptime history

Every Recorded InterExchange Incident

InterExchange incidents, newest first, with date, duration and status.
DateIncidentDurationStatus
Oct 23, 2026App DowntimeThis incident has been resolved.3h 52mResolved
Oct 22, 2026System MaintenanceThe scheduled maintenance has been completed.3h 0mScheduled
Oct 21, 2026App and Passport MaintenanceToday we carried out maintenance in response to security updates within the PHP ecosystem. We have installed the PHP security release published on 21 October on the Passport and Au Pair USA blog servers, and added extra…1h 0mScheduled
Oct 21, 2026Au Pair USA Blog MaintenanceThis incident has been resolved.58 minResolved
Sep 30, 2026Degraded PerformanceThis incident has been resolved.138h 58mResolved
Aug 11, 2026App and Passport System MaintenanceThe scheduled maintenance has been completed.25h 0mScheduled
Jul 3, 2026System MaintenanceThe scheduled maintenance has been completed.2h 0mScheduled
Jul 2, 2026Latent Performance IssuesThis incident has been resolved.20h 8mResolved
Jul 2, 2026Elevated Latency and Packet LossThe upstream incident has been resolved, we have restored services.31 minResolved
Jun 4, 2026Upstream Provider Networking IssuesThis incident has been resolved.1h 24mResolved
May 19, 2026Upstream Provider Networking IssuesThis incident has been resolved.5h 27mResolved
Mar 30, 2026Performance IssuesPast 1 hour normal.2h 55mResolved
Feb 24, 2026App Performance IssuesThis incident has been resolved.10h 8mResolved
Feb 23, 2026Emergency Database MaintenanceThis incident has been resolved.10 minResolved
Feb 21, 2026Connectivity IssuesThis incident has been resolved.79h 56mResolved
Feb 19, 2026Upstream Provider Networking IssuesOur upstream provider has reported full recovery.50 minResolved
Feb 18, 2026Network Connectivity Issues.This incident has been resolved.2h 43mResolved
Feb 12, 2026App ErrorsA fix has been implemented, monitors have been adjusted in response.110h 12mResolved
Feb 11, 2026App ErrorsOur upstream provider has resolved the issues.1h 25mResolved
Feb 11, 2026Passport Network IncidentAll providers reporting operational.1h 38mResolved
Dec 16, 2025Increased Error RatesThe upstream issue has been resolved, all services are operational.6h 38mResolved
Nov 18, 2025Upstream Provider Errors Affecting LoginThe upstream issue has been resolved, all services are operational.4h 38mResolved

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 InterExchange 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 InterExchange 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 InterExchange 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 InterExchange outage in this window ran 5d 18h, against a mean recovery of 19h 15m. If you depend on InterExchange 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.