11 incidente Scrapbox înregistrate începând din aprilie 2021, cu actualizări oficiale, componente afectate, durată și informații despre rezolvare.
We are currently investigating this issue.
The issue has been identified and a fix is being implemented.
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
We are currently investigating this issue.
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
We are currently investigating this issue.
We are continuing to investigate this issue.
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
We are currently investigating this issue.
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
We are currently investigating this issue.
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
We are currently investigating this issue.
The issue has been identified and a fix is being implemented.
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
Scrapbox was inaccessible for an hour. We apologize for the inconvenience. ## What happend * In September, we changed our company credit card * In November, domain payment failed * Due to incorrect settings, payment failures were not properly notified to the developer ## Remediation plan * Fix payment notification settings * If the payment interval is long, such as for a domain, register the schedule in the calendar
The issue has been identified and a fix is being implemented.
DB configuration has been modified and is being deployed.
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
Scrapbox was inaccessible for an hour. We apologize for the inconvenience. ## What happened We deployed two at the same time. * Code for new features * DB index creation code for use in new features A large number of processes requiring a non-existent DB index were running, and the DB hung up. ## Remediation plan Deploy the code that creates the DB index first. Then deploy the new functionality.
The US/EU region of heroku, which we use as our infrastructure, is down. https://status.heroku.com/incidents/2402
Heroku's routing has been recovered. https://status.heroku.com/incidents/2402
This incident has been resolved.
The issue has been identified and a fix is being implemented.
We are continuing to work on a fix for this issue.
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
We are currently investigating this issue.
Added search instance and we are monitoring result.
This incident has been resolved.
