Past Incidents

Identified - Reported failure in DNS name resolution impacting only VPN users using the IP 10.76.19.15 client to zone: sa-east-1a

Feb 25, 13:32 -03

Resolved

Feb 25, 13:37 -03

Identified - Reported failure in DNS name resolution impacting only VPN users using the IP 10.241.240.41 client to zone: sa-east-1a

Feb 25, 13:19 -03

Resolved

Feb 25, 13:24 -03

Identified - Reported failure in DNS name resolution impacting only VPN users using the IP 10.76.19.15 client to zone: sa-east-1a

Feb 25, 13:03 -03

Resolved

Feb 25, 13:08 -03

Identified - Reported failure in DNS name resolution impacting only VPN users using the IP 10.76.19.15 client to zone: sa-east-1a

Feb 25, 12:51 -03

Resolved

Feb 25, 12:56 -03

Identified -

Feb 25, 12:41 -03

Resolved

Feb 25, 12:46 -03

Identified - Reported failure in DNS name resolution impacting only VPN users using the IP 10.76.19.15 client to zone: sa-east-1a

Feb 25, 12:36 -03

Resolved

Feb 25, 12:41 -03

Identified - Reported failure in DNS name resolution impacting only VPN users using the IP 10.241.240.41 client to zone: sa-east-1a

Feb 25, 12:08 -03

Resolved

Feb 25, 12:17 -03

Identified -

Feb 25, 12:06 -03

Resolved

Feb 25, 12:29 -03

Identified - Reported failure in DNS name resolution impacting only VPN users using the IP 10.241.240.41 client to zone: sa-east-1a

Feb 25, 11:56 -03

Resolved

Feb 25, 12:01 -03

Identified - Reported failure in DNS name resolution impacting only VPN users using the IP 10.241.240.41 client to zone: sa-east-1a

Feb 25, 11:47 -03

Resolved

Feb 25, 11:52 -03

Identified - Reported failure in DNS name resolution impacting only VPN users using the IP 10.241.240.41 client to zone: sa-east-1a

Feb 25, 11:33 -03

Resolved

Feb 25, 11:38 -03

Identified -

Feb 25, 11:29 -03

Resolved

Feb 25, 11:56 -03

Identified - Reported failure in DNS name resolution impacting only VPN users using the IP 10.241.240.41 client to zone: sa-east-1a

Feb 25, 11:10 -03

Resolved

Feb 25, 11:15 -03

Identified - GCP VPN is down at region us-central1 at zone southamerica-east1-a

Feb 25, 03:47 -03

Resolved

Feb 25, 03:52 -03

Identified -

Feb 24, 17:39 -03

Resolved

Feb 24, 17:44 -03

Identified -

Feb 24, 17:20 -03

Resolved

Feb 24, 17:35 -03

Identified - We're investigating performance issues on network at zone: sa-east-1a

Feb 21, 20:52 -03

Resolved

Feb 22, 01:52 -03

Identified - Prefixes not received by itc/vpn at zone southamerica-east1-a

Feb 21, 20:51 -03

Resolved

Feb 22, 01:56 -03

Identified - GCP Interconnect is down at region southamerica-east1 at zone southamerica-east1-a

Feb 21, 20:51 -03

Resolved

Feb 22, 01:56 -03

Identified - Prefixes not sent to peer by itx at zone southamerica-east1-a

Feb 21, 20:50 -03

Resolved

Feb 22, 01:55 -03

Identified - The Data Center traffic was switched from ITC link to VPN at southamerica-east1

Feb 21, 20:49 -03

Resolved

Feb 22, 01:59 -03

Identified - The Data Center traffic was switched from DX link to VPN at sa-east-1a

Feb 21, 20:48 -03

Resolved

Feb 22, 01:53 -03

Identified - Reported failure to authenticate on Kubernetes at zone: us-central1-a

Feb 21, 17:00 -03

Resolved

Feb 22, 02:45 -03

Identified - Reported failure to authenticate on Kubernetes at zone: us-central1-a

Feb 21, 17:00 -03

Resolved

Feb 24, 08:25 -03

Identified - Reported failure to authenticate on Kubernetes at zone: us-central1-a

Feb 21, 16:15 -03

Resolved

Feb 21, 16:55 -03

Identified - Reported failure to authenticate on Kubernetes at zone: us-central1-a

Feb 21, 15:58 -03

Identified - Reported failure to authenticate on Kubernetes at zone: us-central1-a

Feb 21, 15:43 -03

Resolved

Feb 21, 15:52 -03

Identified - Prefixes not received by itc/vpn at zone southamerica-east1-a

Feb 21, 15:41 -03

Resolved

Feb 21, 15:46 -03

Identified - Reported failure to authenticate on Kubernetes at zone: us-central1-a

Feb 21, 15:22 -03

Resolved

Feb 21, 15:37 -03

Identified - Reported failure to authenticate on Kubernetes at zone: us-central1-a

Feb 21, 13:58 -03

Resolved

Feb 21, 14:03 -03