Amsterdam (AMS) with Possible Impact
                                    
                                        
                                    
                                    Incident
                                
                            
                        27 November 2022, 03:04  UTC
                    
                Amsterdam (AMS) with Possible Impact
                                    Status: closed
                                
                            
                                    Start:
                                    
                                        27 November 2022, 02:14  UTC
                                    
                                
                            
                                    End:
                                    
                                        27 November 2022, 03:04  UTC
                                    
                                
                            
                                    Duration: 50 minutes
                                
                            
                                Affected Components:
                            
                            
                                            Platform
                                            Europe
                                            Amsterdam (AMS)
                            
                        
                                            Affected Groups:
                                        
                                        
                                                    All Public Users
                                        
                                    
                    
                    Investigating
                    
                27 November 2022, 02:14 UTC
27 November 2022, 02:14 UTC
We're investigating possible performance impact affecting the Amsterdam (AMS) data center.
All other locations and services are unaffected
                    
                    Identified
                    
                27 November 2022, 02:30 UTC
27 November 2022, 02:30 UTC
This issue has been identified and a fix is being implemented.
                    
                    Monitoring
                    
                27 November 2022, 02:50 UTC
27 November 2022, 02:50 UTC
A fix has been implemented and we are monitoring the results.