Maxio 장애 기록

1. 2026년 9월 18일 오후 11:02 UTCinvestigating

   우리는 예상보다 처리 상태에 남아있는 고급 빌링 CSV 수출을 일으키는 문제를 조사하고 있습니다. 우리는 더 많은 정보로 또 다른 업데이트를 제공 할 것입니다.

2. 2026년 9월 18일 오후 11:18 UTCidentified

   문제는 식별되고 수정이 구현됩니다.

3. 2026년 9월 18일 오후 11:32 UTCmonitoring

   수정이 구현되어 결과를 모니터링하고 있습니다.

4. 2026년 9월 18일 오후 11:53 UTCresolved

   고급 빌링 CSV 수출에 영향을 미치는 문제는 해결되고 새로운 수출은 일반적으로 완료됩니다. 수정 이전에 붙어 있던 수출은 완료되지 않으며 제거되고 재 실행되어야 합니다. 우리는 진심으로 혼란에 대한 사과를 받고 우리가이 문제를 해결하기 위해 일하면서 당신의 인내력을 평가합니다.

공식 인시던트 업데이트를 자동 번역했습니다.

1. 2026년 9월 1일 오후 3:40 UTCinvestigating

   Maxio CPQ에 접근하는 문제점을 조사하고 있습니다. 사용자는 현재 애플리케이션에 액세스하려고 할 때 오류가 발생합니다. 우리의 팀은 적극적으로 정상적인 서비스를 복원하고 일하고 있습니다. 더 많은 정보로 추가 업데이트를 제공할 것입니다.

2. 2026년 9월 1일 오후 3:57 UTCmonitoring

   수정이 구현되어 결과를 모니터링하고 있습니다.

3. 2026년 9월 1일 오후 4:11 UTCresolved

   이 사건은 해결되었습니다. 우리는 서비스를 복원하기 위해 일하면서 당신의 인내심을 주셔서 감사합니다, 우리는 진심으로 혼란에 대한 사과.

공식 인시던트 업데이트를 자동 번역했습니다.

1. 2026년 7월 24일 오전 11:21 UTCmonitoring

   우리는 제 3 자 서비스 문제로 인해 Maxio Advanced Billing에 액세스하는 데 영향을 미치는 문제의 인식입니다. 우리는 적극적으로 상황을 모니터링하고 더 많은 정보를 제공 할 것입니다.

2. 2026년 7월 24일 오전 11:32 UTCresolved

   이 사건은 해결되었습니다.

3. 2026년 7월 24일 오전 11:56 UTCpostmortem

   ** 7월 24, 2026**, 10:58 UTC와 11:10 UTC 사이, Maxio Advanced Billing은 제 3 자 서비스 제공 업체 아웃시 문제가 발생하는 간단한 서비스 중단을 경험했습니다. 사건 중, Maxio Advanced Billing API 요청은 실패하거나 오류를 반환 할 수 있습니다. 귀하의 통합이 중단 중에 실패한 API 요청이 발생하면 성공적으로 완료되지 않은 모든 요청을 복원하는 것이 좋습니다. 우리는 불편을 끼쳐 드려서 문제가 조사하고 해결 된 동안 당신의 인내력을 평가합니다.

공식 인시던트 업데이트를 자동 번역했습니다.

1. 2026년 7월 10일 오후 3:07 UTCinvestigating

   We are currently investigating this issue.

2. 2026년 7월 10일 오후 3:08 UTCmonitoring

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

3. 2026년 7월 10일 오후 3:11 UTCresolved

   This incident has been resolved.

1. 2026년 7월 7일 오전 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. 2026년 6월 19일 오후 5:59 UTCinvestigating

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

2. 2026년 6월 19일 오후 6:42 UTCinvestigating

   We are continuing to investigate this issue.

3. 2026년 6월 19일 오후 7:17 UTCmonitoring

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

4. 2026년 6월 19일 오후 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. 2026년 6월 15일 오후 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. 2026년 6월 15일 오후 7:50 UTCidentified

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

3. 2026년 6월 15일 오후 8:21 UTCmonitoring

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

4. 2026년 6월 15일 오후 8:25 UTCresolved

   This incident has been resolved.

1. 2026년 6월 10일 오후 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. 2026년 6월 10일 오후 7:27 UTCidentified

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

3. 2026년 6월 10일 오후 7:58 UTCmonitoring

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

4. 2026년 6월 10일 오후 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. 2026년 5월 22일 오후 1:18 UTCresolved

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

1. 2026년 5월 8일 오후 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. 2026년 5월 8일 오후 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. 2026년 4월 20일 오후 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. 2026년 4월 20일 오후 4:53 UTCinvestigating

   We are continuing to investigate this issue.

3. 2026년 4월 20일 오후 4:58 UTCidentified

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

4. 2026년 4월 20일 오후 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. 2026년 4월 20일 오후 5:34 UTCresolved

   This incident has been resolved.

1. 2026년 4월 13일 오후 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. 2026년 4월 13일 오후 5:54 UTCmonitoring

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

3. 2026년 4월 13일 오후 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. 2026년 4월 13일 오후 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. 2026년 4월 14일 오전 7:02 UTCresolved

   This incident has been resolved.

1. 2026년 4월 1일 오후 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. 2026년 4월 1일 오후 3:25 UTCinvestigating

   We are continuing to investigate this issue.

3. 2026년 4월 1일 오후 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. 2026년 4월 1일 오후 4:51 UTCmonitoring

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

5. 2026년 4월 1일 오후 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. 2026년 4월 1일 오후 8:58 UTCresolved

   This incident has been resolved.

1. 2026년 2월 11일 오후 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. 2026년 2월 11일 오후 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. 2026년 2월 11일 오후 6:20 UTCresolved

   This incident has been resolved.

1. 2026년 2월 4일 오전 12:58 UTCinvestigating

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

2. 2026년 2월 4일 오전 1:25 UTCinvestigating

   We are continuing to investigate this issue.

3. 2026년 2월 4일 오전 1:28 UTCidentified

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

4. 2026년 2월 4일 오전 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. 2026년 1월 27일 오후 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. 2026년 1월 21일 오후 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. 2026년 1월 21일 오후 8:13 UTCidentified

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

3. 2026년 1월 21일 오후 9:03 UTCmonitoring

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

4. 2026년 1월 21일 오후 9:11 UTCresolved

   This incident has been resolved.

1. 2026년 1월 17일 오전 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. 2026년 1월 8일 오후 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. 2026년 1월 8일 오후 3:39 UTCidentified

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

3. 2026년 1월 8일 오후 3:41 UTCmonitoring

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

4. 2026년 1월 8일 오후 3:43 UTCresolved

   This incident has been resolved.

1. 2025년 12월 3일 오후 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. 2025년 12월 3일 오후 9:55 UTCmonitoring

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

3. 2025년 12월 3일 오후 9:55 UTCmonitoring

   We are continuing to monitor for any further issues.

4. 2025년 12월 3일 오후 10:30 UTCresolved

   This incident has been resolved.