Is Swapcard down?

Last checked 1m ago
Current status
Swapcard is up

No incidents right now.

Official status page: https://www.swapcardstatus.com · Polled every 5 minutes · 15 components tracked

Swapcard is operational right now. Last checked 1m ago; the most recent incident resolved 7d ago.

Real-time Swapcard status, recent outages, and incident history — pulled directly from Swapcard's official status page at https://www.swapcardstatus.com every 5 minutes. Pingoru tracks 15 Swapcard services and has captured 4 incidents in the last 90 days (99.56% uptime). Get email, Slack, Discord, or webhook alerts the moment Swapcard reports a new incident — free for 5 monitors, no credit card.

Users who monitor Swapcard also follow these Video services: Vimeo GoToMeeting WeVideo Twitch Plex Sinch Frame.io Streamlabs Airtame Mux View all 6,000+ providers
Swapcard uptime 99.56% uptime · past 90 days
Mon Wed Fri
JunJulAugSep
Less More

Recent outages & incidents

Past 90 days
  1. Resolved
    Started Sep 11, 2026, 10:29 AM UTC · Resolved Sep 11, 2026, 10:29 AM UTC
    StudioEvent AppExhibitor Center
    Timeline · 2 updates
    • investigating · Sep 11, 2026, 10:28 AM UTC

      Status: Investigating We are currently investigating this issue. Affected components Studio (Partial outage) Event App (Partial outage) Exhibitor Center (Partial outage)

    • resolved · Sep 11, 2026, 10:29 AM UTC

      Status: Resolved This incident has been resolved. Affected components Studio (Operational) Event App (Operational) Exhibitor Center (Operational)

    Latest: Status: Resolved This incident has been resolved. Affected components Studio (Operational) Event App (Operational) Exhibitor Center (Operational)

  2. Resolved
    Started Sep 08, 2026, 09:04 AM UTC · Resolved Sep 08, 2026, 09:04 AM UTC
    Timeline · 3 updates
    • identified · Sep 08, 2026, 09:01 AM UTC

      Status: Identified The issue has been identified and a fix is being implemented.

    • monitoring · Sep 08, 2026, 09:02 AM UTC

      Status: Monitoring A fix has been implemented. We are working on restoring the analytics data, there are no data loss during the process.

    • resolved · Sep 08, 2026, 09:04 AM UTC

      Status: Resolved This incident has been resolved.

    Latest: Status: Resolved This incident has been resolved.

  3. Resolved
    Started Aug 31, 2026, 12:01 PM UTC · Resolved Aug 31, 2026, 12:01 PM UTC
    Timeline · 1 update
    • resolved · Aug 31, 2026, 12:01 PM UTC

      Status: Resolved On Monday 31 August, exhibitors and organizers scanning badges began seeing an error after a scan, with the scan then stored as an offline scan on the device. This happened on devices with a working internet connection, which is why it was initially mistaken for a venue network problem. On iOS, some devices showed only a red banner that did not open when tapped. No lead data was lost. Two mechanisms protected the data at the same time. Server side, each lead was saved to our primary database at the moment of the scan, before the step that failed, so the lead already existed even when the app reported an error. Device side, the app's offline mode captured the scan and synced it once scanning recovered. Because a repeat submission of the same scan updates the existing lead rather than adding a new one, this did not create duplicate leads. The cause was specific to the badge scanning path. Registration, event pages, meetings, messaging, exports and the organizer back-office were not affected during this window.

    Latest: Status: Resolved On Monday 31 August, exhibitors and organizers scanning badges began seeing an error after a scan, with the scan then stored as an offline scan on the device. This…

  4. Resolved
    Started Jul 01, 2026, 07:48 PM UTC · Resolved Jul 01, 2026, 07:48 PM UTC
    Timeline · 3 updates
    • identified · Jul 01, 2026, 05:37 PM UTC

      Status: Identified Sherlock is currently experiencing degraded performance due to an inference capacity issue. We are working with our inference providers to restore full capacity as quickly as possible.

    • identified · Jul 01, 2026, 07:08 PM UTC

      Status: Identified A fix to increase capacity is currently under testing.

    • resolved · Jul 01, 2026, 07:48 PM UTC

      Status: Resolved Inference capacity has been fully restored

    Latest: Status: Resolved Inference capacity has been fully restored

Outage history

Past 90 days · 4 incidents View full outage history →