NeoAirline incident

Elevated errors with vAMSYS API

Resolved after 1 hour 21 minutes, affecting section-318076 (vAMSYS Sync) and section-318076 (vAMSYS Sync), on April 18, 2026.

resolved Apr 18, 2026, 03:38 PM UTC

We've identified the issue with vAMSYS sync, and it should be solved now. We're monitoring the fix.

Started
Apr 18, 2026, 02:17 PM UTC
Resolved
Apr 18, 2026, 03:38 PM UTC
Duration
1h 21m
Detected by Pingoru
Apr 18, 2026, 02:17 PM UTC

Affected components

section-318076 (vAMSYS Sync)section-318076 (vAMSYS Sync)

Update timeline

  1. investigating Apr 18, 2026, 02:17 PM UTC

    Our team is investigating an issue where some of the routes' syncs are getting elevated errors when syncing to vAMSYS.

  2. resolved Apr 18, 2026, 03:38 PM UTC

    We've identified the issue with vAMSYS sync, and it should be solved now. We're monitoring the fix.

Your product runs on more than NeoAirline

Add the vendors you depend on and get one message when any of them reports trouble. Free for 3 vendors, no card.

Add your stack →