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
Aug 09, 19:39 -03
Resolved
Aug 12, 08:34 -03
DNSDNSLdapCorpPartialOutage
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
Aug 09, 16:49 -03
Resolved
Aug 09, 17:39 -03
DNSDNSLdapCorpPartialOutage
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
Aug 09, 16:23 -03
Resolved
Aug 09, 16:28 -03
Thursday 8th August 2024
DNSDNSLdapCorpPartialOutage
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
Aug 08, 18:54 -03
Resolved
Aug 09, 14:34 -03
DNSDNSLdapCorpPartialOutage
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
Aug 08, 18:14 -03
Resolved
Aug 08, 18:19 -03
DNSDNSLdapCorpPartialOutage
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
Aug 08, 16:09 -03
Resolved
Aug 08, 16:39 -03
Wednesday 7th August 2024
NetworkApiLatency
Identified - We're investigating a slow response from API at zone: us-central1-a
Aug 07, 13:38 -03
Resolved
Aug 07, 13:43 -03
Tuesday 6th August 2024
DNSDNSLdapCorpPartialOutage
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
Aug 06, 17:02 -03
Resolved
Aug 06, 18:02 -03
NetworkApiLatency
Identified - We're investigating a slow response from API at zone: southamerica-east1-a
Aug 06, 04:42 -03
Resolved
Aug 06, 04:47 -03
Monday 5th August 2024
DNSDNSLdapCorpPartialOutage
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
Aug 05, 18:49 -03
Resolved
Aug 05, 19:24 -03
NetworkGCP_BgppeerRcd_dev
Identified - Prefixes not received by itc/vpn at zone southamerica-east1-a
Aug 05, 17:51 -03
Resolved
Aug 05, 18:11 -03
NetworkGCP_VPN_Dev_Up
Identified - GCP VPN is down at region us-central1 at zone southamerica-east1-a
Aug 05, 17:50 -03
Resolved
Aug 05, 18:10 -03
NetworkGCP_BgppeerSnd_Dev
Identified - Prefixes not sent to peer by vpn at zone southamerica-east1-a
Aug 05, 17:27 -03
Resolved
Aug 05, 18:12 -03
NetworkConnectionMajorOutage
Identified - We're investigating a failure to communicate with all datacenter vlans at zone: us-central1-a
Aug 05, 17:24 -03
Resolved
Aug 05, 17:29 -03
DNSDNSLdapCorpPartialOutage
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
Aug 05, 16:02 -03
Resolved
Aug 05, 16:07 -03
DNSDNSLdapCorpPartialOutage
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
Aug 05, 14:21 -03
Resolved
Aug 05, 14:41 -03
IngressAccessFromInternet
Identified - We're investigating a reported failure to access kubernetes from internet at zone: southamerica-east1-a
Aug 05, 10:50 -03
Resolved
Aug 05, 10:55 -03
NetworkConnectionMajorOutage
Identified - We're investigating a failure to communicate with all datacenter vlans at zone: us-central1-a
Aug 05, 03:05 -03
Resolved
Aug 05, 03:10 -03
Sunday 4th August 2024
NetworkGCP_BgppeerRcd_prd
Identified - Prefixes not received by itc/vpn at zone southamerica-east1-a
Aug 04, 18:02 -03
Resolved
Aug 04, 18:07 -03
NetworkGCP_VPN_Dev_Up
Identified - GCP VPN is down at region us-central1 at zone southamerica-east1-a
Aug 04, 18:02 -03
Resolved
Aug 04, 18:07 -03
NetworkConnectionMajorOutage
Identified - We're investigating a failure to communicate with all datacenter vlans at zone: us-central1-a