Past Incidents

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

Sep 26, 09:39 -03

Resolved

Sep 26, 09:54 -03

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

Sep 26, 09:29 -03

Resolved

Sep 26, 09:34 -03

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

Sep 26, 06:05 -03

Resolved

Sep 26, 06:10 -03

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

Sep 26, 02:11 -03

Resolved

Sep 26, 02:16 -03

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

Sep 25, 19:26 -03

Resolved

Sep 25, 19:31 -03

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

Sep 25, 19:10 -03

Resolved

Sep 25, 19:20 -03

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

Sep 25, 13:51 -03

Resolved

Sep 25, 14:01 -03

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

Sep 25, 12:14 -03

Resolved

Sep 25, 12:19 -03

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

Sep 24, 20:55 -03

Resolved

Sep 24, 21:00 -03

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

Sep 24, 16:36 -03

Resolved

Sep 24, 16:41 -03

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

Sep 24, 14:04 -03

Resolved

Sep 24, 14:09 -03

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

Sep 24, 12:39 -03

Resolved

Sep 24, 13:14 -03

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

Sep 24, 10:24 -03

Identified - We're investigating a reported failure to access Kubernetes API at zone: sa-east-1a

Sep 24, 10:08 -03

Resolved

Sep 24, 10:18 -03

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

Sep 24, 09:29 -03

Resolved

Sep 24, 10:07 -03

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

Sep 24, 04:38 -03

Resolved

Sep 24, 04:43 -03

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

Sep 24, 02:22 -03

Resolved

Sep 24, 02:27 -03

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

Sep 23, 23:23 -03

Resolved

Sep 24, 01:08 -03

Identified - GCP Interconnect attachment has low traffic at region southamerica-east1 at zone southamerica-east1-a

Sep 23, 22:24 -03

Resolved

Sep 24, 01:09 -03

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

Sep 23, 22:18 -03

Resolved

Sep 24, 01:08 -03

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

Sep 23, 22:17 -03

Resolved

Sep 24, 01:07 -03

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

Sep 23, 22:15 -03

Resolved

Sep 24, 01:10 -03

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

Sep 23, 21:20 -03

Resolved

Sep 23, 21:35 -03

Identified -

Sep 23, 16:56 -03

Resolved

Sep 23, 17:11 -03

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

Sep 23, 13:46 -03

Resolved

Sep 23, 13:51 -03

Identified - We're investigating a slow response from API at zone: southamerica-east1-a

Sep 23, 07:03 -03

Resolved

Sep 23, 07:08 -03

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

Sep 23, 06:33 -03

Resolved

Sep 23, 06:38 -03

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

Sep 23, 02:37 -03

Resolved

Sep 23, 02:42 -03

Identified - We're investigating a slow response from API at zone: southamerica-east1-a

Sep 22, 12:33 -03

Resolved

Sep 22, 12:38 -03

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

Sep 22, 10:35 -03

Resolved

Sep 22, 10:40 -03

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

Sep 22, 07:09 -03

Resolved

Sep 22, 07:14 -03

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

Sep 21, 08:40 -03

Resolved

Sep 21, 08:45 -03

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

Sep 21, 07:41 -03

Resolved

Sep 21, 07:46 -03

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

Sep 21, 06:01 -03

Resolved

Sep 21, 06:06 -03

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

Sep 21, 01:30 -03

Resolved

Sep 21, 01:35 -03

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

Sep 20, 19:41 -03

Resolved

Sep 20, 19:46 -03

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

Sep 20, 14:45 -03

Resolved

Sep 20, 14:50 -03

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

Sep 20, 13:45 -03

Resolved

Sep 20, 13:50 -03

Identified - We're investigating a slow response from API at zone: southamerica-east1-a

Sep 20, 13:35 -03

Resolved

Sep 20, 13:40 -03

Identified - We're investigating a slow response from API at zone: southamerica-east1-a

Sep 20, 03:47 -03

Resolved

Sep 20, 03:52 -03

Identified - We're investigating a slow response from API at zone: southamerica-east1-a

Sep 20, 02:23 -03

Resolved

Sep 20, 02:28 -03

Identified - We're investigating a slow response from API at zone: southamerica-east1-a

Sep 20, 01:03 -03

Resolved

Sep 20, 01:08 -03

Identified - We're investigating a slow response from API at zone: southamerica-east1-a

Sep 20, 00:23 -03

Resolved

Sep 20, 00:28 -03

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

Sep 19, 22:55 -03

Resolved

Sep 20, 00:05 -03

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

Sep 19, 22:55 -03

Resolved

Sep 20, 00:05 -03

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

Sep 19, 22:54 -03

Resolved

Sep 20, 00:04 -03

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

Sep 19, 22:53 -03

Resolved

Sep 20, 00:08 -03

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

Sep 19, 22:10 -03

Resolved

Sep 19, 22:20 -03

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

Sep 19, 22:09 -03

Resolved

Sep 19, 22:19 -03

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

Sep 19, 21:16 -03

Resolved

Sep 19, 21:21 -03