Home
/
Status
/
Service
Integrated software solutions for communities and organizations.
Source
auto
Category
Analytics
Adapter
STATUSPAGE IO
Verified
Pending review
Current state
Operational
Checked 12m ago
16
Components
0
Active incidents
2
Maintenance
7.69%
90d uptime
[SEV-3] Togetherpay - Intermittent Processing Issues
May 29, 2:15 PM
Normalized official status-page data for incidents, maintenance, components, and history.
7.69%
Known uptime
13 known history days
16
Components tracked
0 outage, 0 degraded
50
Incidents indexed
0 active right now
52
Maintenance windows
2 active or scheduled
Components with the most recent status-page events.
Merchant Endpoints
Operational
Payment Tokenization
Operational
ProPay Production Environment
Operational
Togetherpay API - Production
Operational
Transaction Processing
Operational
Component changes, incidents, and maintenance windows grouped by day.
operational
degraded
outage
maintenance
unknown
1
operational days
0
degraded days
3
outage days
9
maintenance days
77
unknown days
Latest outages and degradations detected from the official status page.
ProPay implemented a fix and transactions are no longer intermittently timing out. A total of 38 transactions were affected between 9:05 a.m.-10:35 a.m. eastern. This incident is resolved.
ProPay confirmed the chargeback issue has been resolved. They are still assessing the scope and impact of the issue. We will share additional details as they become available from ProPay.
All regular settlement files, comprehensive reports and merchant settlement files are now available. This incident is resolved.
Settlement files, comprehensive reports and merchant settlement files are now available for consumption. This incident is resolved.
Settlement files, comprehensive reports and merchant settlement files are now available for consumption. This incident is resolved.
An effort to clean up merchant level users in Togetherpay led to the archiving of inactive users - those that had not logged in for over one year and those that have never logged in. Identified user records were archived. This inadvertently broke authentication for Togetherpay merchant API calls, because some of the archived user records were actually merchant API keys. Work to restore the archived users led to additional issues including database connectivity errors and replica host failures. The incident was resolved by reverting the affected user records and fixing database replica configurations. Teams evaluated the sequence of events and implemented steps to prevent such events from happening in the future.
The intermittent processing issue was limited to Canadian accounts. A very limited number of transactions were affected between 10:22 a.m. - 12:27 p.m. eastern. ProPay resolved the issue. This incident is resolved.
ProPay has implemented a fix and is will continue to monitor the results. At this time this incident is resolved.
ProPay implemented a fix which appears to have fixed the problem. The last transaction to timeout was at 4:59 p.m. eastern. Processing is back to normal.
All regular settlement files and merchant settlement files are now available. This incident is resolved.
Scheduled and completed maintenance windows are separated from incidents.
ProPay is planning a maintenance event to their production environment on Thursday, June 25, from 2:00 a.m. - 7:00 a.m. eastern. While ProPay does not anticipate any interruption in service, a certain amount of risk exists with any maintenance event.
Togetherwork is planning an update to the Togetherpay production environment on Tuesday, June 23 between 1:00 a.m. - 3:00 a.m. eastern. The nature of the update will require up to a 60 minute outage which will cause Togetherpay to be unavailable during this time.
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 Togetherwork status page, normalizes upstream events, and separates incidents from scheduled maintenance.
Official source
https://status.togetherwork.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.
Showing 1 to 16 of 16 tracked components.
| Component | Status | Type | Last changed |
|---|---|---|---|
Togetherpay API - Production | Operational | Group | 6/18/2026 |
Togetherpay Client Application | Operational | Group | Not recorded |
Togetherpay API - Testing Environments | Operational | Group | Not recorded |
Integration Test Environment | Operational | Component | Not recorded |
Togetherpay Web Front-End (TPA) | Operational | Component | Not recorded |
Transaction Processing The internal mechanisms that Togetherpay relies on to transmit payments from a merchant or affiliate to the upstream processor. As measured by: Transaction processing is not completing, is degraded, or is unavailable for any reason. | Operational | Component | 6/18/2026 |
File Import Process - Internal The import process used by Togetherpay OpCos to download and import transaction records provided by Togetherpay for the purpose of settlement, fee correlation, or other information needed from the payment gateway. As measured by: File import process does not complete at the desired time or file endpoints are unavailable or responding in a degraded capacity | Operational | Component | Not recorded |
Sandbox Test Environment | Operational | Component | Not recorded |
Payment Tokenization This is the end-to-end process that allows consumers of Togetherpay to securely transmit payment data to the processor and receive non-sensitive payment tokens to prevent the storage of highly sensitive CHD (Card Holder Data) As measured by: Payment method tokenization is not completing, is degraded, or is unavailable for any reason. | Operational | Component | 6/18/2026 |
ProPay Testing Environments | Operational | Component | Not recorded |
Togetherwork Marketing Site | Operational | Component | Not recorded |
Transaction or Payment Method Listings A mission critical function of the application is to allow OpCo staff to review transactions and payment methods. The application must be able to provide access to this data in a reasonable time in a non-programmatic way. As measured by: Transaction or payment method listings are unavailable or responding in a degraded capacity | Operational | Component | Not recorded |
File Import Process - External The import process used by Togetherpay to download and import transaction records provided by the processor for the purpose of settlement, fee correlation, or other information needed from the payment processor. As measured by: File import process does not complete at the desired time or file endpoints are unavailable or responding in a degraded capacity | Operational | Component | 6/18/2026 |
Merchant Endpoints These are the endpoints critical to creating and updating merchants using the API. This is considered a critical function of our Togetherpay customers. This covers the ability to Add, Edit, or Remove merchants used in Togetherpay. As measured by: Requests that Merchants be created or updated are not completing, is degraded, or is unavailable for any reason. | Operational | Component | 6/18/2026 |
Togetherpay Documentation Site The documentation site is critical for our customers and integration teams using the platform. It should have an SLA similar to a critical internal system. As measured by: Documentation site is unavailable or responding in a degraded capacity. | Operational | Component | Not recorded |
ProPay Production Environment | Operational | Component | 6/18/2026 |
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.
Togetherwork 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.
