VIpps/MobilePay errors
This incident has been resolved.
Home
/
Status
/
Service
Fundraising platform for highly engaged supporters.
Source
auto
Category
Development
Adapter
STATUSPAGE IO
Verified
Pending review
Current state
Operational
Checked 4m ago
8
Components
0
Active incidents
0
Maintenance
100%
90d uptime
VIpps/MobilePay errors
Jan 19, 10:45 AM
Normalized official status-page data for incidents, maintenance, components, and history.
100%
Known uptime
1 known history days
8
Components tracked
0 outage, 0 degraded
50
Incidents indexed
0 active right now
50
Maintenance windows
0 active or scheduled
Components with the most recent status-page events.
AWS cloudFront
Operational
AWS ec2-eu-west-1
Operational
AWS route53
Operational
BetterNow Platform
Operational
Donation Payment Processing
Operational
Component changes, incidents, and maintenance windows grouped by day.
operational
degraded
outage
maintenance
unknown
1
operational days
0
degraded days
0
outage days
0
maintenance days
89
unknown days
Latest outages and degradations detected from the official status page.
This incident has been resolved.
This incident has been resolved.
This incident has been resolved.
This incident has been resolved.
This incident has been resolved.
This incident has been resolved.
An error in a deploy caused an increased error rate for API requests to the fundraisers endpoint. The deploy has been rolled back as of 15:22 CEST
This incident has been resolved.
This incident has been resolved.
Swish has resolved their incident. We continue to monitor the error rate for Swish payments. https://status.swish.nu/incidents/1fwn9ny2lsh3
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.
The scheduled maintenance has been completed.
The scheduled maintenance has been completed.
The scheduled maintenance has been completed.
The scheduled maintenance has been completed.
Uptimus tracks the official Betternow status page, normalizes upstream events, and separates incidents from scheduled maintenance.
Official source
https://status.betternow.org
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.
Showing 1 to 8 of 8 tracked components.
| Component | Status | Type | Last changed |
|---|---|---|---|
BetterNow Platform | Operational | Component | Not recorded |
api.betternow.org Public BetterNow API | Operational | Component | Not recorded |
Donation Payment Processing | Operational | Component | Not recorded |
images.yourbetternow.org Image CDN and upload service | Operational | Component | Not recorded |
AWS ec2-eu-west-1 | Operational | Component | Not recorded |
AWS cloudFront | Operational | Component | Not recorded |
AWS route53 | Operational | Component | Not recorded |
Heroku | Operational | Component | Not recorded |
Follow outages, degraded components, and maintenance updates in your Uptimus workspace with email, push, and webhook alerts.
Official provider components
Incident and maintenance separation
Workspace alerts and webhooks
Related status pages based on category, adapter type, and operational history.
Betternow 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.