Kubernetes Status Page

No incidents reported

Network GCP_VPN_Dev_Up

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

Sep 07, 10:51 -03

Resolved

Sep 07, 10:56 -03

Network ConnectionMajorOutage

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

Sep 07, 10:48 -03

Resolved

Sep 07, 10:53 -03

DNS DNSQueryUOLCorpUsersVPN_PartialOutage

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

Sep 06, 16:07 -03

Resolved

Sep 09, 11:15 -03

Network GCP_BgppeerRcd_prd

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

Sep 06, 02:16 -03

Resolved

Sep 06, 02:21 -03

Network ConnectionMajorOutage

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

Sep 06, 02:12 -03

Resolved

Sep 06, 02:17 -03

Kubernetes Infrastructure Upgrade without outage at southamerica-east1-a and us-central1-a, scheduled 10 months ago

We're performing an operating system upgrade without outage at southamerica-east1-a and us-central1-a

Network ConnectionMajorOutage

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

Sep 05, 18:16 -03

Resolved

Sep 05, 18:21 -03

NetworkPolicy ACL

Identified - We're investigating a failure on NetworkPolicy at zone: us-central1-a

Sep 05, 15:26 -03

Resolved

Sep 09, 11:15 -03

Network ConnectionMajorOutage

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

Sep 04, 23:15 -03

Resolved

Sep 04, 23:20 -03

Network ApiLatency

Identified - We're investigating a slow response from API at zone: sa-east-1a

Sep 04, 17:31 -03

Resolved

Sep 04, 17:36 -03

Authentication LoginFailure

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

Sep 04, 16:23 -03

Resolved

Sep 04, 17:28 -03

Network GCP_BgppeerRcd_dev

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

Sep 04, 16:05 -03

Resolved

Sep 04, 16:15 -03

Network GCP_BgppeerSnd_Dev

Identified - Prefixes not sent to peer by vpn at zone us-central1-a

Sep 04, 16:05 -03

Resolved

Sep 04, 16:15 -03

Network GCP_Router_Dev_Up

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

Sep 04, 15:09 -03

Resolved

Sep 04, 15:14 -03

DNS DNSQueryUOLCorpUsersVPN_PartialOutage

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 03, 20:07 -03

Resolved

Sep 04, 09:37 -03

DNS InternalDNSisUnhealthy

Identified - Internal Cluster DNS is falling for kubernetes local services queries

Sep 03, 16:13 -03

Resolved

Sep 03, 16:18 -03

DNS DNSQueryUOLCorpUsersVPN_PartialOutage

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 03, 12:05 -03

Resolved

Sep 03, 12:15 -03

Network GCP_BgppeerRcd_prd

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

Sep 03, 09:51 -03

Resolved

Sep 03, 09:56 -03

Network ConnectionMajorOutage

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

Sep 03, 09:46 -03

Resolved

Sep 03, 09:51 -03

Network GCP_BgppeerRcd_prd

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

Sep 03, 01:25 -03

Resolved

Sep 03, 01:30 -03

Network ConnectionMajorOutage

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

Sep 03, 01:21 -03

Resolved

Sep 03, 01:26 -03

DNS DNSQueryUOLCorpUsersVPN_PartialOutage

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 02, 16:54 -03

Resolved

Sep 02, 18:24 -03

DNS DNSQueryUOLCorpUsersVPN_PartialOutage

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 02, 16:22 -03

Resolved

Sep 02, 16:27 -03

DNS DNSQueryUOLCorpUsersVPN_PartialOutage

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 02, 11:19 -03

Resolved

Sep 02, 11:29 -03

Past Incidents

Sunday 8th September 2024

Saturday 7th September 2024

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

Resolved

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

Resolved

Friday 6th September 2024

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

Resolved

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

Resolved

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

Resolved

Thursday 5th September 2024

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

Resolved

Identified - We're investigating a failure on NetworkPolicy at zone: us-central1-a

Resolved

Wednesday 4th September 2024

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

Resolved

Identified - We're investigating a slow response from API at zone: sa-east-1a

Resolved

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

Resolved

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

Resolved

Identified - Prefixes not sent to peer by vpn at zone us-central1-a

Resolved

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

Resolved

Tuesday 3rd September 2024

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

Resolved

Identified - Internal Cluster DNS is falling for kubernetes local services queries

Resolved

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

Resolved

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

Resolved

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

Resolved

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

Resolved

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

Resolved

Monday 2nd September 2024

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

Resolved

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

Resolved

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

Resolved