Teampay Outage History

Teampay is up right now

Teampay had 3 outages in the last 2 years totaling 54h 47m of downtime — averaging 0.1 incidents per month.

There were 3 Teampay outages since July 2, 2025 totaling 54h 47m of downtime. Each is summarised below — incident details, duration, and resolution information.

Source: https://status.teampay.co

Major November 18, 2025

Upstream ACH provider outage

Detected by Pingoru
Nov 18, 2025, 02:07 PM UTC
Resolved
Nov 18, 2025, 06:13 PM UTC
Duration
4h 5m
Affected: Dwolla
Timeline · 3 updates
  1. investigating Nov 18, 2025, 02:07 PM UTC

    An outage from an upstream provider may impact ACH payments. We are monitoring the situation.

  2. investigating Nov 18, 2025, 02:11 PM UTC

    We are continuing to investigate this issue.

  3. resolved Nov 18, 2025, 06:13 PM UTC

    The outage from the upstream provider is resolved. We are still monitoring the situation.

Read the full incident report →

Minor October 20, 2025

AWS outage

Detected by Pingoru
Oct 20, 2025, 04:11 PM UTC
Resolved
Oct 21, 2025, 03:31 PM UTC
Duration
23h 19m
Affected: Web ApplicationTeampayGo iOS ApplicationMarqeta
Timeline · 2 updates
  1. monitoring Oct 20, 2025, 04:11 PM UTC

    Numerous AWS services are still degraded which may impact Teampay services such as virtual card creation.

  2. resolved Oct 21, 2025, 03:31 PM UTC

    AWS and Marqeta are back up. Teampay is reconciling data impacted by the outage.

Read the full incident report →

Minor July 2, 2025

Bank Login Provider down

Detected by Pingoru
Jul 02, 2025, 10:38 PM UTC
Resolved
Jul 04, 2025, 02:00 AM UTC
Duration
1d 3h
Affected: Web Application
Timeline · 3 updates
  1. identified Jul 02, 2025, 10:38 PM UTC

    An issue with our bank login provider is impacting the following features: - No new bank accounts can be added via bank login provider - Historical transaction pulls via bank login are broken We are currently working with the provider and will update our status page as updates become available. The Teampay application remains operational aside from this issue.

  2. identified Jul 04, 2025, 01:56 AM UTC

    The issue has been resolved and all systems are operational.

  3. resolved Jul 04, 2025, 02:00 AM UTC

    The issue has been resolved and all systems are operational.

Read the full incident report →