Home
/
Status
/
Service
Digital commerce platform for software and SaaS companies.
Source
auto
Category
Payments
Adapter
STATUSPAGE IO
Verified
Pending review
Current state
Operational
Checked 42m ago
1
Components
0
Active incidents
0
Maintenance
33.33%
90d uptime
Drop in Amazon order completion rates
May 23, 6:00 PM
Component changes, incidents, and maintenance windows grouped by day.
operational
degraded
outage
maintenance
unknown
Showing 1 to 1 of 1 tracked components.
| Component | Status | Type | Last changed |
|---|---|---|---|
FastSpring System | Operational | Component | Not recorded |
Follow outages, degraded components, and maintenance updates in your Uptimus workspace with email, push, and webhook alerts.
Related status pages based on category, adapter type, and operational history.
Fastspring is currently marked as Operational in Uptimus based on the latest official status page check.
Supported status page providers are checked continuously by our scraper scheduler. The public page is cached briefly for SEO and performance.
No. Uptimus stores incidents and maintenance windows separately when the upstream provider exposes enough detail.
Yes. Create an Uptimus workspace, follow this provider, and choose email, push, or webhook notifications.
Normalized official status-page data for incidents, maintenance, components, and history.
33.33%
Known uptime
3 known history days
1
Components tracked
0 outage, 0 degraded
50
Incidents indexed
0 active right now
17
Maintenance windows
0 active or scheduled
Components with the most recent status-page events.
FastSpring System
Operational
1
operational days
0
degraded days
1
outage days
1
maintenance days
87
unknown days
Latest outages and degradations detected from the official status page.
We observed a drop in Amazon order completion rates and investigated the issue. However, the issue is now resolved. Amazon orders are currently processing normally, and the error is no longer being observed.
This incident has been resolved.
During a routine maintenance release, from 12:25 pm PT to 02:00 pm PT, our system encountered an error where some buyer emails failed to be sent. The change has been reverted, and we can confirm buyer emails are successfully being sent.
Operations and services are back to normal.
Our Engineers are not seeing any continuing impact. Ebanx confirmed on their status page that their systems are now functioning normally. Cloudflare has also confirmed that the issue is resolved and things are back to how it was pre-incident. We consider this issue resolved.
Webhook latency is gradually returning to normal levels. All subscription rebills are currently processing, and we will continue to monitor the system for any further issues.
All services are operating normally, except for a delay in processing rebills. Our team is actively working to resolve this and ensure all affected transactions are completed as soon as possible.
We are no longer seeing the error in our logs and PayPal orders are completing successfully
This incident has been resolved.
Paypal is reporting the incident as resolved, see https://www.paypal-status.com/history/production
Scheduled and completed maintenance windows are separated from incidents.
The scheduled maintenance has been completed.
The scheduled maintenance has been completed.
The scheduled maintenance has been completed.
The scheduled maintenance has been completed.
The scheduled maintenance has been completed.
The scheduled maintenance has been completed.
Activities are complete.
The scheduled maintenance is complete. During the process there were two outages of about one minute each. No further impact is expected.
The scheduled maintenance has been completed.
The scheduled maintenance has been completed.
Uptimus tracks the official Fastspring status page, normalizes upstream events, and separates incidents from scheduled maintenance.
Official source
https://status.fastspring.com
Adapter
STATUSPAGE IO
Alert streams
Incidents, component changes, and maintenance windows.
Public SEO page
Indexable status history for users searching outage information.
Regional reports can be layered on top of official provider status when user signals are available.
Official provider components
Incident and maintenance separation
Workspace alerts and webhooks
