Live  /  FastSpring  /  Incident

FastSpring: Google Pay Disruption

FastSpring · fastspring.comMajor incidentResolved2026-09-16 16:20 UTC
Public — what happened

Summary

FastSpring posted a major-severity notice about a Google Pay disruption starting on September 16, 2026 at 16:20 UTC, passing along a message it received from Google. According to that message, a majority of users of several Google Pay services on Android and the web, including payment button, readiness checks, payment data loading and Secure Payment Authentication, could still reach them but were running into errors, slow responses or other odd behavior. No cause was given, and while the status was still listed as investigating, the incident was marked resolved at 17:06 the same day.

Timeline

Source of record: provider status page. Summary written by SquidGrid from the provider’s published updates; times in UTC.

Independent path health

The status page is the symptom. SquidGrid measures the paths that reach FastSpring against their own baselines — whether the routes carrying your traffic degraded, at which handoff, and who owns that stretch.

🔒 Sign in to see
Customers get the live Provider Assessment Report for FastSpring: its full incident track record, what tends to break, and recent public reports of problems.

Included with any paid plan.

Open the FastSpring report →

More from FastSpring

Covered in The Squid’s Ink, Week 39, 2026, our weekly internet health report.

The full archive is on the FastSpring status & history page.

Related: FastSpring status & history. SquidGrid is not affiliated with FastSpring.