Ιστορικό διακοπών του Maxio

1. 1 Σεπτεμβρίου 2026 στις 3:40 μ.μ. UTCinvestigating

   Ερευνούμε ένα θέμα που επηρεάζει την πρόσβαση στο Maxio CPQ. Οι χρήστες βιώνουν σήμερα σφάλματα κατά την προσπάθεια πρόσβασης στην εφαρμογή. Η ομάδα μας ερευνά ενεργά και εργάζεται για την αποκατάσταση της κανονικής υπηρεσίας. Θα παρέχουμε πρόσθετες ενημερώσεις καθώς θα γίνονται διαθέσιμες περισσότερες πληροφορίες.

2. 1 Σεπτεμβρίου 2026 στις 3:57 μ.μ. UTCmonitoring

   Εφαρμόστηκε μια ρύθμιση και παρακολουθούμε τα αποτελέσματα.

3. 1 Σεπτεμβρίου 2026 στις 4:11 μ.μ. UTCresolved

   Το περιστατικό λύθηκε. Σας ευχαριστούμε για την υπομονή σας, ενώ εργαστήκαμε για την αποκατάσταση της υπηρεσίας, και ειλικρινά συγγνώμη για την αναστάτωση.

Αυτόματη μετάφραση από την επίσημη ενημέρωση του συμβάντος.

1. 24 Ιουλίου 2026 στις 11:21 π.μ. UTCmonitoring

   Γνωρίζουμε και ερευνούμε θέματα που επηρεάζουν την πρόσβαση στην Maxio Advanced Billing λόγω ενός θέματος υπηρεσιών τρίτων. Παρακολουθούμε ενεργά την κατάσταση και θα παρέχουμε ενημερώσεις καθώς θα γίνονται διαθέσιμες περισσότερες πληροφορίες.

2. 24 Ιουλίου 2026 στις 11:32 π.μ. UTCresolved

   Το περιστατικό λύθηκε.

3. 24 Ιουλίου 2026 στις 11:56 π.μ. UTCpostmortem

   Στις 24 Ιουλίου 2026**, μεταξύ 10:58 UTC και 11:10 UTC, ο Maxio Advanced Billing γνώρισε μια σύντομη διακοπή της υπηρεσίας που προκλήθηκε από ένα ζήτημα με διακοπή παροχής υπηρεσιών από τρίτους. Κατά τη διάρκεια του περιστατικού, οι αιτήσεις API για Maxio Advanced Billing μπορεί να έχουν αποτύχει ή επιστρέψει λάθη. Εάν οι ενσωματώσεις σας συνάντησαν αποτυχημένα αιτήματα API κατά τη διάρκεια της διακοπής, σας συνιστούμε να δοκιμάσετε ξανά τυχόν αιτήματα που δεν ολοκληρώθηκαν επιτυχώς. Ζητάμε συγγνώμη για την ταλαιπωρία και εκτιμούμε την υπομονή σας ενώ το θέμα ερευνήθηκε και επιλύθηκε.

Αυτόματη μετάφραση από την επίσημη ενημέρωση του συμβάντος.

1. 10 Ιουλίου 2026 στις 3:07 μ.μ. UTCinvestigating

   We are currently investigating this issue.

2. 10 Ιουλίου 2026 στις 3:08 μ.μ. UTCmonitoring

   A fix has been implemented and we are monitoring the results.

3. 10 Ιουλίου 2026 στις 3:11 μ.μ. UTCresolved

   This incident has been resolved.

1. 7 Ιουλίου 2026 στις 11:55 π.μ. UTCresolved

   Maxio Core encountered issues with UI Elements not displaying correctly within the application. Our engineering team quickly identified and resolved the issue.

1. 19 Ιουνίου 2026 στις 5:59 μ.μ. UTCinvestigating

   We are currently investigating reports of e-invoice emails not being sent.

2. 19 Ιουνίου 2026 στις 6:42 μ.μ. UTCinvestigating

   We are continuing to investigate this issue.

3. 19 Ιουνίου 2026 στις 7:17 μ.μ. UTCmonitoring

   A fix has been implemented and we are monitoring the results.

4. 19 Ιουνίου 2026 στις 9:36 μ.μ. UTCresolved

   This incident has been resolved. As part of our remediation efforts, we identified invoices impacted by the issue and are actively resending any affected e-Bills that had not already been resent manually after the fix was released. No further customer action is required at this time. We apologize for the disruption this caused and appreciate your patience while our team investigated and resolved the issue.

1. 15 Ιουνίου 2026 στις 7:30 μ.μ. UTCinvestigating

   We are currently investigating an issue affecting the Maxio HubSpot integration. Some merchants may be unable to create subscriptions from HubSpot deals. Our team has identified a likely source of the issue and is actively working on mitigation. We will provide another update once we have more information.

2. 15 Ιουνίου 2026 στις 7:50 μ.μ. UTCidentified

   The issue has been identified and a fix is being implemented.

3. 15 Ιουνίου 2026 στις 8:21 μ.μ. UTCmonitoring

   A fix has been implemented and we are monitoring the results.

4. 15 Ιουνίου 2026 στις 8:25 μ.μ. UTCresolved

   This incident has been resolved.

1. 10 Ιουνίου 2026 στις 6:58 μ.μ. UTCidentified

   A recent API behavior change is causing some merchant requests with unexpected or unsupported fields to fail with validation errors (422 responses). This is impacting multiple workflows and merchants, including the HubSpot integration. We have identified the underlying issue and are actively working to restore expected behavior as quickly as possible.

2. 10 Ιουνίου 2026 στις 7:27 μ.μ. UTCidentified

   We are continuing to work on a fix for this issue.

3. 10 Ιουνίου 2026 στις 7:58 μ.μ. UTCmonitoring

   A fix has been implemented and we are monitoring the results.

4. 10 Ιουνίου 2026 στις 8:47 μ.μ. UTCresolved

   This incident has been resolved. Our team has implemented a fix and confirmed that impacted requests are processing normally again, including affected integration workflows. We sincerely apologize for the disruption and appreciate your patience while we worked to restore service.

1. 22 Μαΐου 2026 στις 1:18 μ.μ. UTCresolved

   Maxio encountered issues with icons not displaying within the application. Our engineering team quickly identified and resolved the issue.

1. 8 Μαΐου 2026 στις 1:44 μ.μ. UTCinvestigating

   We are currently investigating elevated 503 errors. Some customers may experience intermittent errors or degraded availability. Our engineering team is actively working to identify the root cause and mitigate the impact. We will provide another update as soon as we have more information.

2. 8 Μαΐου 2026 στις 2:15 μ.μ. UTCresolved

   The incident causing unexpected 503 errors during today’s platform release has been resolved. Some customers may continue to briefly experience cached errors for the next few minutes as systems fully recover.

1. 20 Απριλίου 2026 στις 4:24 μ.μ. UTCinvestigating

   We are currently investigating an issue where some Advanced Billing invoices are returning 500 errors when accessed via the application UI. Our team is actively working to identify the root cause. We will provide updates as more information becomes available.

2. 20 Απριλίου 2026 στις 4:53 μ.μ. UTCinvestigating

   We are continuing to investigate this issue.

3. 20 Απριλίου 2026 στις 4:58 μ.μ. UTCidentified

   The issue has been identified and a fix is being implemented.

4. 20 Απριλίου 2026 στις 5:29 μ.μ. UTCmonitoring

   A fix has been implemented and we are currently monitoring the results. Our investigation determined that the 502 errors were caused by timeouts and occurred for users when viewing consolidated invoices directly in the application UI or when accessing invoice PDFs via the API. While initial reports suggested broader API impact, we have since confirmed that standard invoice API endpoints and public invoice URLs were not affected, with the exception of PDF retrieval. No underlying invoice data was impacted.

5. 20 Απριλίου 2026 στις 5:34 μ.μ. UTCresolved

   This incident has been resolved.

1. 13 Απριλίου 2026 στις 5:29 μ.μ. UTCidentified

   We are currently investigating and fixing an issue impacting E-Billing where customers may encounter errors when attempting to access e-billing related pages. Thank you for your patience while we work to resolve this.

2. 13 Απριλίου 2026 στις 5:54 μ.μ. UTCmonitoring

   A fix has been implemented and we are monitoring the results.

3. 13 Απριλίου 2026 στις 6:07 μ.μ. UTCmonitoring

   We have implemented a partial fix for an issue impacting E-Billing where customers may encounter errors when attempting to access e-billing related pages. We are continuing to investigate and work on additional changes to fully resolve the issue.

4. 13 Απριλίου 2026 στις 8:39 μ.μ. UTCmonitoring

   We have implemented changes to address an issue impacting E-Billing where customers may encounter errors when attempting to access e-billing related pages. We are monitoring progress as updates continue to take effect. Thank you for your patience.

5. 14 Απριλίου 2026 στις 7:02 π.μ. UTCresolved

   This incident has been resolved.

1. 1 Απριλίου 2026 στις 3:25 μ.μ. UTCinvestigating

   We are currently investigating degraded performance impacting some areas of our system, which may affect processing times and related functionality. Our team is actively working to restore normal performance as quickly as possible. We will continue to share updates as we have more information. Thank you for your patience.

2. 1 Απριλίου 2026 στις 3:25 μ.μ. UTCinvestigating

   We are continuing to investigate this issue.

3. 1 Απριλίου 2026 στις 4:06 μ.μ. UTCidentified

   We have identified the issue causing degraded system performance. Our team is actively working on implementing a solution, and you may start seeing improvements as we continue to restore normal performance. We will continue to share updates as progress is made. Thank you for your patience.

4. 1 Απριλίου 2026 στις 4:51 μ.μ. UTCmonitoring

   A fix has been implemented and we are monitoring the results.

5. 1 Απριλίου 2026 στις 8:58 μ.μ. UTCmonitoring

   The root cause of the issue has been fully identified and resolved, and system performance has returned to normal. We have been monitoring closely and are confident the platform is operating as expected. No action is required at this time. Thank you for your patience.

6. 1 Απριλίου 2026 στις 8:58 μ.μ. UTCresolved

   This incident has been resolved.

1. 11 Φεβρουαρίου 2026 στις 6:00 μ.μ. UTCidentified

   Earlier today, we released an update to our Stripe integration within Advanced Billing to support enhanced validation requirements for Commercial Enhanced Data Program (CEDP) data. This update introduced an unintended regression that caused some payments to fail due to stricter validation of certain line-item values. This behavior is limited to Stripe processing within Advanced Billing. We are in the process reverting the release to restore normal processing and will provide an update once the rollback is complete.

2. 11 Φεβρουαρίου 2026 στις 6:17 μ.μ. UTCmonitoring

   We have rolled back the earlier release that caused Stripe payment failures within Advanced Billing. Payment processing has been restored and we are actively monitoring. Any payments that failed due to this issue can now be safely retried, either manually or through automatic dunning where enabled. We sincerely apologize for the disruption and appreciate your patience.

3. 11 Φεβρουαρίου 2026 στις 6:20 μ.μ. UTCresolved

   This incident has been resolved.

1. 4 Φεβρουαρίου 2026 στις 12:58 π.μ. UTCinvestigating

   We are currently investigating reports of Integration syncs and exports not running in the Maxio Platform.

2. 4 Φεβρουαρίου 2026 στις 1:25 π.μ. UTCinvestigating

   We are continuing to investigate this issue.

3. 4 Φεβρουαρίου 2026 στις 1:28 π.μ. UTCidentified

   The issue has been identified and a fix is being implemented.

4. 4 Φεβρουαρίου 2026 στις 1:33 π.μ. UTCresolved

   We have deployed a fix and this incident is now resolved. Background jobs for integration syncs and exports/imports are running normally again. We will also be implementing additional safeguards to help prevent this issue from recurring.

1. 27 Ιανουαρίου 2026 στις 4:50 μ.μ. UTCresolved

   Resolved — Advanced Billing experienced a very brief period of degraded performance lasting approximately 1 minute and 10 seconds between 01:32 UTC and 01:33 UTC on 1/27/2026. During this time, some requests may have returned 500-level responses. Normal processing continued, and the service quickly returned to full operational status.

1. 21 Ιανουαρίου 2026 στις 8:08 μ.μ. UTCinvestigating

   We’re currently investigating an issue where the horizontal scroll bar is missing on the Create Transactions screen (including when creating contracts with transactions), which prevents users from scrolling to view and enter values in all required columns.

2. 21 Ιανουαρίου 2026 στις 8:13 μ.μ. UTCidentified

   The issue has been identified and a fix is being implemented.

3. 21 Ιανουαρίου 2026 στις 9:03 μ.μ. UTCmonitoring

   A fix has been implemented and we are monitoring the results.

4. 21 Ιανουαρίου 2026 στις 9:11 μ.μ. UTCresolved

   This incident has been resolved.

1. 17 Ιανουαρίου 2026 στις 9:29 π.μ. UTCresolved

   Between 2026-01-17 06:40:01 UTC and 2026-01-17 08:51:29 UTC Advanced Billing merchants using exchange rates experienced intermittent HTTP 500 errors on the Product Catalog and Subscription API endpoints due to a third-party service disruption with Open Exchange Rates. No data loss occurred (request/response errors only). This was mitigated on our end as of 2026-01-17 08:51:29 UTC, and service is operating normally.

1. 8 Ιανουαρίου 2026 στις 3:32 μ.μ. UTCinvestigating

   We are currently investigating an issue preventing some customers from adding ACH info via Plaid to pay e-Bills and update their e-Bill Billing Profile.

2. 8 Ιανουαρίου 2026 στις 3:39 μ.μ. UTCidentified

   The issue has been identified and a fix is being implemented.

3. 8 Ιανουαρίου 2026 στις 3:41 μ.μ. UTCmonitoring

   A fix has been implemented and we are monitoring the results.

4. 8 Ιανουαρίου 2026 στις 3:43 μ.μ. UTCresolved

   This incident has been resolved.

1. 3 Δεκεμβρίου 2025 στις 9:27 μ.μ. UTCidentified

   We are currently experiencing unexpected errors related to today’s release that may prevent some users from logging in or navigating the system. Our development team is actively investigating the cause and working to restore full functionality as quickly as possible. We will continue to share updates as we make progress. Thank you for your patience.

2. 3 Δεκεμβρίου 2025 στις 9:55 μ.μ. UTCmonitoring

   A fix has been implemented and we are monitoring the results.

3. 3 Δεκεμβρίου 2025 στις 9:55 μ.μ. UTCmonitoring

   We are continuing to monitor for any further issues.

4. 3 Δεκεμβρίου 2025 στις 10:30 μ.μ. UTCresolved

   This incident has been resolved.

1. 24 Νοεμβρίου 2025 στις 10:11 μ.μ. UTCresolved

   Summary An update released earlier today introduced an unintended regression that caused human verification checks (via reCAPTCHA) to fail in Chargify.js. This prevented successful payment profile tokenizations with Chargify.js, and also prevented some customers from completing signups on Public Signup Pages and from updating payment information in the Billing Portal. Affected customers encountered an error stating that verification could not be completed. Impact From 11:43 AM CDT to 1:36 PM CDT, reCAPTCHA verification failed on pages utilizing Chargify.js, including in cases where the feature was not enabled. This blocked form submissions for impacted customers during that period. Resolution The issue was identified and the update responsible was promptly reverted, restoring normal functionality. Next Steps We are enhancing our release and validation processes to prevent similar issues in the future. We sincerely apologize for the disruption and appreciate your patience as we worked to address this matter.