Varago experienced a minor incident on May 16, 2024 affecting Vagaro Pro App and Vagaro Clients App, lasting 6h 31m. The incident has been resolved; the full update timeline is below.
Affected components
Update timeline
- investigating May 16, 2024, 04:54 PM UTC
We are aware that some customers are experiencing minor performance issues with our service. Please be assured that our team of dedicated engineers is actively addressing the issue. We understand the inconvenience this may cause and we sincerely apologize for any disruption to your experience. We appreciate your patience and understanding during this time. We will provide the next update shortly. Thank you for your continued support.
- investigating May 16, 2024, 05:28 PM UTC
We are continuing to investigate this issue. Next update will be posted within 30 min. Thank you for your continued patience.
- identified May 16, 2024, 06:15 PM UTC
Our Engineering team is still actively working on resolving the issue. Next Update within 30 min. Thank you for your continued patience.
- investigating May 16, 2024, 06:48 PM UTC
Our Engineering team is still actively working on resolving the issue. Next Update within 30 min. Thank you for your continued patience.
- identified May 16, 2024, 07:32 PM UTC
Our Engineering team has identified the root issue and is actively working on resolving the issue. Next Update within 30 min. Thank you for your continued patience.
- identified May 16, 2024, 08:08 PM UTC
Our Engineering team has identified the root issue and is still working on resolving the issue. We will provide another update within 30 min. Thank you for your continued patience.
- identified May 16, 2024, 08:50 PM UTC
Our Engineering team is still working on resolving the issue. We will provide another update within 30 min. Thank you for your continued patience.
- monitoring May 16, 2024, 10:55 PM UTC
Our Engineering team has applied the solution and is currently monitoring the outcome. We'll share another update within 30 minutes. Thank you for your ongoing patience.
- resolved May 16, 2024, 11:59 PM UTC
This incident has now been resolved. Thank you very much for your cooperation and we apologize for any inconvenience.