All systems are operational

Past Incidents

Sunday 23rd June 2024

No incidents reported

Saturday 22nd June 2024

Network GCP_Router_Dev_Up
Identified - Sum of GCP Cloud Router instances at zone southamerica-east1-a is mismatched

Jun 22, 13:24 -03

Resolved

Jun 22, 13:29 -03

Friday 21st June 2024

Network ConnectionMajorOutage
Identified - We're investigating a failure to communicate with all datacenter vlans at zone: us-central1-a

Jun 21, 18:05 -03

Resolved

Jun 21, 18:10 -03

Thursday 20th June 2024

DNS DNSLdapCorpPartialOutage
Identified - We're investigating a reported failure in DNS name resolution impacting only VPN users using the IP 192.168.150.10 client to zone: southamerica-east1-a

Jun 20, 05:53 -03

Resolved

Jun 20, 05:58 -03

Wednesday 19th June 2024

Authentication LoginFailure
Identified - We're investigating a failure to authenticate on Kubernetes at zone: us-central1-a

Jun 19, 20:28 -03

Resolved

Jun 19, 20:43 -03

Authentication LoginFailure
Identified - We're investigating a failure to authenticate on Kubernetes at zone: sa-east-1a

Jun 19, 20:26 -03

Resolved

Jun 19, 20:41 -03

Authentication LoginFailure
Identified - We're investigating a failure to authenticate on Kubernetes at zone: southamerica-east1-a

Jun 19, 20:25 -03

Resolved

Jun 19, 20:40 -03

DNS DNSLdapCorpPartialOutage
Identified - We're investigating a reported failure in DNS name resolution impacting only VPN users using the IP 192.168.150.10 client to zone: us-central1-a

Jun 19, 07:54 -03

Resolved

Jun 19, 08:49 -03

DNS DNSLdapCorpPartialOutage
Identified - We're investigating a reported failure in DNS name resolution impacting only VPN users using the IP 192.168.150.10 client to zone: us-central1-a

Jun 19, 07:08 -03

Resolved

Jun 19, 07:33 -03

DNS DNSLdapCorpPartialOutage
Identified - We're investigating a reported failure in DNS name resolution impacting only VPN users using the IP 192.168.150.10 client to zone: us-central1-a

Jun 19, 05:59 -03

Resolved

Jun 19, 06:49 -03

DNS DNSLdapCorpPartialOutage
Identified - We're investigating a reported failure in DNS name resolution impacting only VPN users using the IP 192.168.150.10 client to zone: us-central1-a

Jun 19, 04:15 -03

Resolved

Jun 19, 05:40 -03

DNS DNSLdapCorpPartialOutage
Identified - We're investigating a reported failure in DNS name resolution impacting only VPN users using the IP 192.168.150.10 client to zone: us-central1-a

Jun 19, 03:44 -03

Resolved

Jun 19, 03:54 -03

DNS DNSLdapCorpPartialOutage
Identified - We're investigating a reported failure in DNS name resolution impacting only VPN users using the IP 192.168.150.10 client to zone: us-central1-a

Jun 19, 02:44 -03

Resolved

Jun 19, 02:59 -03

DNS DNSLdapCorpPartialOutage
Identified - We're investigating a reported failure in DNS name resolution impacting only VPN users using the IP 192.168.150.10 client to zone: us-central1-a

Jun 19, 02:04 -03

Resolved

Jun 19, 02:14 -03

DNS DNSLdapCorpPartialOutage
Identified - We're investigating a reported failure in DNS name resolution impacting only VPN users using the IP 192.168.150.10 client to zone: us-central1-a

Jun 19, 00:54 -03

Resolved

Jun 19, 01:44 -03

DNS DNSLdapCorpPartialOutage
Identified - We're investigating a reported failure in DNS name resolution impacting only VPN users using the IP 192.168.150.10 client to zone: us-central1-a

Jun 19, 00:14 -03

Resolved

Jun 19, 00:34 -03

Tuesday 18th June 2024

DNS DNSLdapCorpPartialOutage
Identified - We're investigating a reported failure in DNS name resolution impacting only VPN users using the IP 192.168.150.10 client to zone: us-central1-a

Jun 18, 23:05 -03

Resolved

Jun 18, 23:50 -03

DNS DNSLdapCorpPartialOutage
Identified - We're investigating a reported failure in DNS name resolution impacting only VPN users using the IP 192.168.150.10 client to zone: us-central1-a

Jun 18, 21:35 -03

Resolved

Jun 18, 22:35 -03

DNS DNSLdapCorpPartialOutage
Identified - We're investigating a reported failure in DNS name resolution impacting only VPN users using the IP 192.168.150.10 client to zone: us-central1-a

Jun 18, 19:55 -03

Resolved

Jun 18, 21:10 -03

DNS DNSLdapCorpPartialOutage
Identified - We're investigating a reported failure in DNS name resolution impacting only VPN users using the IP 192.168.150.10 client to zone: us-central1-a

Jun 18, 18:17 -03

DNS DNSLdapCorpPartialOutage
Identified - We're investigating a reported failure in DNS name resolution impacting only VPN users using the IP 192.168.150.10 client to zone: sa-east-1a

Jun 18, 17:44 -03

Resolved

Jun 18, 17:49 -03

DNS DNSLdapCorpPartialOutage
Identified - We're investigating a reported failure in DNS name resolution impacting only VPN users using the IP 10.241.240.41 client to zone: us-central1-a

Jun 18, 17:14 -03

Resolved

Jun 18, 18:00 -03

DNS DNSLdapCorpPartialOutage
Identified - We're investigating a reported failure in DNS name resolution impacting only VPN users using the IP 10.241.240.42 client to zone: us-central1-a

Jun 18, 16:39 -03

Resolved

Jun 18, 16:59 -03

DNS DNSLdapCorpPartialOutage
Identified - We're investigating a reported failure in DNS name resolution impacting only VPN users using the IP 10.241.240.42 client to zone: us-central1-a

Jun 18, 15:34 -03

Resolved

Jun 18, 16:19 -03

DNS DNSLdapCorpPartialOutage
Identified - We're investigating a reported failure in DNS name resolution impacting only VPN users using the IP 10.241.240.41 client to zone: us-central1-a

Jun 18, 14:59 -03

Resolved

Jun 18, 15:14 -03

DNS DNSLdapCorpPartialOutage
Identified - We're investigating a reported failure in DNS name resolution impacting only VPN users using the IP 10.241.240.41 client to zone: us-central1-a

Jun 18, 14:32 -03

Resolved

Jun 18, 14:42 -03

DNS DNSLdapCorpPartialOutage
Identified - We're investigating a reported failure in DNS name resolution impacting only VPN users using the IP 10.241.240.41 client to zone: us-central1-a

Jun 18, 14:03 -03

Resolved

Jun 18, 14:13 -03

DNS DNSLdapCorpPartialOutage
Identified - We're investigating a reported failure in DNS name resolution impacting only VPN users using the IP 10.241.240.42 client to zone: us-central1-a

Jun 18, 12:31 -03

Resolved

Jun 18, 13:46 -03

DNS DNSLdapCorpPartialOutage
Identified - We're investigating a reported failure in DNS name resolution impacting only VPN users using the IP 10.241.240.42 client to zone: us-central1-a

Jun 18, 11:41 -03

Resolved

Jun 18, 12:21 -03

Monday 17th June 2024

No incidents reported