Joined July 2024
1 Photos and videos
[status] Resolved: We have identified that the core problem is related to the Intermittent dashboard failures. Please follow status.sentry.io/incidents/z… for the latest updates. In the meantime, this will be marked as resolved. stspg.io/6frmvhqsv7xt
184
[status] Investigating: We also identified that transaction ingestion was also affected. stspg.io/6frmvhqsv7xt
147
Sentry Support retweeted
Feb 18
Founders Dev Leaders: clear your cals for Nothing but (inter)net, a live gathering for minds behind the monitors šŸ‘Øā€šŸ’»šŸ§™ā€ā™‚ļø Featuring @WesBos and @STolinski from @Syntaxfm, @Teej_dv and @ThePrimeagen from The Standup, and @JamesACowling, Founder of @Convex, in conversation with @zeeg, Founder of Sentry. Plus a Golden State Warriors legend appearance šŸ‘€ šŸ“ Chase Center (Above the Rim) šŸ—“ļø March 27 | 3–6 PM Food. Drinks. SWAG. Seating is limited! RSVP here: luma.com/everythinginternet
4
10
63
61,232
[status] Completed: The scheduled maintenance has been completed. stspg.io/x6v4nm1fvs02
120
[status] In progress: We completed the brownout successfully. The involved DNS records are back to the previous addresses and the schedule for the final switch has been confirmed for Tuesday, January 13th, 08:00-19:00 UTC. stspg.io/x6v4nm1fvs02
89
[status] In progress: Scheduled maintenance is currently in progress. We will provide updates as necessary. stspg.io/x6v4nm1fvs02
49
[status] Scheduled: Maintenance will begin as scheduled in 60 minutes. stspg.io/x6v4nm1fvs02
40
[status] Resolved: We had a database corruption where new org creation, user sign-ups, new API Token generation, and new integrations made between 3:45PM and 5:00PM PST were affected and will need to be re-created. No other data were affected. We are very sorry for this inconvenience. stspg.io/n5lznyjz415l
41
[status] Monitoring: We restored the impacted services to operational state, while investigating the full impact of the incident stspg.io/n5lznyjz415l
42
[status] Monitoring: We are continuing to monitor for any further issues. stspg.io/n5lznyjz415l
28
[status] Monitoring: We implemented a fix for the issue and monitoring stspg.io/n5lznyjz415l
34
[status] Identified: We're implementing a fix for the issue stspg.io/n5lznyjz415l
46
[status] Investigating: We detected a data corruption in one of our databases and investigating the issue stspg.io/n5lznyjz415l
1
321
[status] Resolved: This incident has been resolved. stspg.io/7qqf3vfq9wln

32
[status] Monitoring: We're continuing to process the backlog of errors and transactions. New events will be processed in a timely fashion. stspg.io/7qqf3vfq9wln

29
[status] Monitoring: We are continuing to work through backlogs in errors and transactions. Profiles, attachments and replays have recovered. stspg.io/7qqf3vfq9wln

29
[status] Identified: Ingestion has resumed and we are continuing to monitor and restore full service. stspg.io/7qqf3vfq9wln

26
[status] Identified: We have identified the source of the issue and are scaling up infrastructure to restore service stspg.io/7qqf3vfq9wln

19
[status] Investigating: We're investigating an unavailable system in our ingestion pipelines. stspg.io/7qqf3vfq9wln

15