The Atlanta, Dallas, Newark and Toronto probe locations are being updated and given additional capacity.
During the update customers may see a brief gap in their metrics of no more than one sample. The next test execution may schedule slightly sooner or slightly later ( +/- 1 minute ), before returning to the normal test execution frequency.
This update will refresh all IPv4 addresses and IPv6 addresses for these locations. In preparation for the migration https://allowlists.grafana.com/synthetics has been updated with new ranges, or refer to the new CIDR below:
Atlanta "ipv4":["45.79.200.81/32","45.79.200.246/32","45.79.200.104/32","172.105.148.64/32","45.79.200.41/32"], "ipv6":["2600:3c02::f03c:95ff:fe0e:7724/128","2600:3c02::f03c:95ff:fe0e:7765/128","2600:3c02::f03c:95ff:fe0e:77b3/128","2600:3c02::f03c:95ff:fe0e:7701/128","2600:3c02::f03c:95ff:fe0e:771d/128"]
Toronto "ipv4":["192.46.223.60/32","172.105.22.39/32","172.105.16.250/32","172.105.101.57/32"], "ipv6":["2600:3c04::f03c:95ff:fe0e:77b9/128","2600:3c04::f03c:95ff:fe0e:77fc/128","2600:3c04::f03c:95ff:fe0e:773a/128","2600:3c04::f03c:95ff:fe0e:7700/128"] Posted on
Oct 16, 2024 - 01:58 UTC
The Frankfurt probe will be migrating from Digital Ocean to AWS in order to improve its scalability, reliability, and functionality. This change will bring static IPv4 addresses and IPv6 CIDR ranges for more reliable allow-listing, make k6-powered scripted and browser synthetics available in these locations, and upgrade the probe to a new public probe architecture with improved reliability.
For allow-listing, the new CIDR ranges for Frankfurt will be: "ipv4": ["3.123.217.248/32","54.93.147.62/32"], "ipv6": ["2a05:d014:241:5760::/60","2a05:d014:241:5770::/60"]
During the switchover customers may see a brief gap in their metrics of no more than one sample. The next test execution may schedule slightly sooner or slightly later ( +/- 1 minute ), before returning to the normal test execution frequency. Posted on
Oct 02, 2024 - 20:53 UTC
The Amsterdam, Bangalore, New York, San Francisco probe locations are being updated and given additional capacity.
During the update customers may see a brief gap in their metrics of no more than one sample. The next test execution may schedule slightly sooner or slightly later ( +/- 1 minute ), before returning to the normal test execution frequency.
This update will refresh all IPv4 addresses and IPv6 addresses for these locations. In preparation for the migration https://allowlists.grafana.com/synthetics has been updated with new ranges, or refer to the new CIDR below:
New York "ipv4":["159.223.152.78/32","159.223.135.84/32","159.223.175.146/32","159.223.141.217/32","159.223.171.3/32","159.223.158.138/32"], "ipv6":["2604:a880:400:d1::388d:d001/128","2604:a880:400:d1::388d:b001/128","2604:a880:400:d1::388d:e001/128","2604:a880:400:d1::388e:1/128","2604:a880:400:d1::388d:a001/128","2604:a880:400:d1::388d:f001/128"]
San Francisco "ipv4":["157.245.178.143/32","157.245.186.8/32","157.245.171.185/32","157.245.190.119/32"], "ipv6":["2604:a880:2:d1::eab:6001/128","2604:a880:2:d1::eab:7001/128","2604:a880:2:d1::eab:5001/128","2604:a880:2:d1::eab:8001/128"] Posted on
Oct 16, 2024 - 01:58 UTC
The Tokyo probe will be migrating from Linode to AWS in order to improve its scalability, reliability, and functionality. This change will bring static IPv4 addresses and IPv6 CIDR ranges for more reliable allow-listing, make k6-powered scripted and browser synthetics available in these locations, and upgrade the probe to a new public probe architecture with improved reliability.
For allow-listing, the new CIDR ranges for Tokyo will be: "ipv4": ["52.193.17.93/32","52.68.38.219/32"], "ipv6": ["2406:da14:d5b:c560::/60","2406:da14:d5b:c570::/60"]
During the switchover customers may see a brief gap in their metrics of no more than one sample. The next test execution may schedule slightly sooner or slightly later ( +/- 1 minute ), before returning to the normal test execution frequency. Posted on
Oct 02, 2024 - 20:55 UTC
This should last around 20 minutes, during which users won't be able to create new external snapshots on this instance or access existing ones. Everything will return to normal when the upgrade is over.
Creating or accessing snapshots on your personal instance will still be available. Posted on
Oct 17, 2024 - 09:22 UTC
Completed -
The scheduled maintenance has been completed.
Oct 22, 15:30 UTC
In progress -
Scheduled maintenance is currently in progress. We will provide updates as necessary.
Oct 22, 14:30 UTC
Scheduled -
The Singapore probe will be migrating from Digital Ocean to AWS in order to improve its scalability, reliability, and functionality. This change will bring static IPv4 addresses and IPv6 CIDR ranges for more reliable allow-listing, make k6-powered scripted and browser synthetics available in these locations, and upgrade the probe to a new public probe architecture with improved reliability.
For allow-listing, the new CIDR ranges for Singapore will be: "ipv4": ["13.228.17.76/32","18.139.143.38/32"], "ipv6": ["2406:da18:883:9960::/60","2406:da18:883:9970::/60"]
During the switchover customers may see a brief gap in their metrics of no more than one sample. The next test execution may schedule slightly sooner or slightly later ( +/- 1 minute ), before returning to the normal test execution frequency.
Oct 2, 20:51 UTC
Resolved -
Engineering has released a fix and as of 19:20 UTC, customers should no longer experience any issues with the MS SQL plugin. At this time, we are considering this issue resolved. No further updates.
Oct 17, 19:21 UTC
Identified -
As of 14.50UTC, we became aware of an issue with the MS SQL plugin released to Grafana Cloud instances running daily or instant release schedule. Engineering is actively engaged and has identified the issue. We will provide updates accordingly.
Oct 17, 15:01 UTC
Completed -
The scheduled maintenance has been completed.
Oct 17, 09:30 UTC
In progress -
Scheduled maintenance is currently in progress. We will provide updates as necessary.
Oct 17, 08:30 UTC
Scheduled -
We want to make you aware that on 17th of October at 8:30 UTC, there will be a scheduled downtime for approximately 1 hour. We will be using this time for internal infrastructure upgrades. Running k6 test-runs could be affected and marked as `Aborted by the System`.
Oct 10, 14:16 UTC
Completed -
The migration of London to AWS is complete
Oct 16, 14:10 UTC
In progress -
Scheduled maintenance is currently in progress. We will provide updates as necessary.
Oct 16, 13:00 UTC
Scheduled -
The London probe will be migrating from Linode to AWS in order to improve its scalability, reliability, and functionality. This change will bring static IPv4 addresses and IPv6 CIDR ranges for more reliable allow-listing, make k6-powered scripted and browser synthetics available in these locations, and upgrade the probe to a new public probe architecture with improved reliability.
For allow-listing, the new CIDR ranges for London will be: "ipv4": ["18.170.156.12/32","3.9.11.243/32"], "ipv6": ["2a05:d01c:5b3:4060::/60","2a05:d01c:5b3:4070::/60"]
During the switchover customers may see a brief gap in their metrics of no more than one sample. The next test execution may schedule slightly sooner or slightly later ( +/- 1 minute ), before returning to the normal test execution frequency.
Oct 2, 20:47 UTC
Completed -
The scheduled maintenance has been completed.
Oct 15, 16:30 UTC
In progress -
Scheduled maintenance is currently in progress. We will provide updates as necessary.
Oct 15, 15:30 UTC
Scheduled -
The Mumbai probe will be migrating from Linode to AWS in order to improve its scalability, reliability, and functionality. This change will bring static IPv4 addresses and IPv6 CIDR ranges for more reliable allow-listing, make k6-powered scripted and browser synthetics available in these locations, and upgrade the probe to a new public probe architecture with improved reliability.
For allow-listing, the new CIDR ranges for Mumbai will be: "ipv4": ["35.154.231.90/32","15.206.42.88/32"] "ipv6": ["2406:da1a:944:3e60::/60","2406:da1a:944:3e70::/60"]
During the switchover customers may see a brief gap in their metrics of no more than one sample. The next test execution may schedule slightly sooner or slightly later ( +/- 1 minute ), before returning to the normal test execution frequency.
Oct 2, 20:37 UTC
Resolved -
The fix has been rolled out and issue has been reoslved.
Oct 12, 12:14 UTC
Identified -
The issue has been identified and a fix is being implemented
Oct 12, 11:40 UTC
Investigating -
AWS Tempo cells currently do not support the ALPN protocol on our HTTP/2 endpoint, leading to failures in queries sent through hosted Grafana. This issue manifests as failed ALPN checks, resulting in authentication handshake errors when accessing Tempo data. We are currently investigating this issue.
Oct 12, 11:16 UTC
Completed -
The scheduled maintenance is complete.
Oct 11, 16:35 UTC
In progress -
Scheduled maintenance is currently in progress. We will provide updates as necessary.
Oct 11, 13:00 UTC
Scheduled -
The Sydney probe will be migrating from Linode to AWS in order to improve its scalability, reliability, and functionality. This change will bring static IPv4 addresses and IPv6 CIDR ranges for more reliable allow-listing, make k6-powered scripted and browser synthetics available in these locations, and upgrade the probe to a new public probe architecture with improved reliability.
For allow-listing, the new CIDR ranges for Sydney will be: "ipv4": ["52.63.27.15/32","54.206.232.254/32"] "ipv6": ["2406:da1c:235:8b60::/60","2406:da1c:235:8b70::/60"]
During the switchover customers may see a brief gap in their metrics of no more than one sample. The next test execution may schedule slightly sooner or slightly later ( +/- 1 minute ), before returning to the normal test execution frequency.
Oct 2, 20:35 UTC
Resolved -
At approximately ~11:30 UTC some customers in the prod-us-east-0 region experienced either extremely slow Loki queries, or Loki queries not returning at all. This lasted until ~ 15:30 UTC when the fix was rolled out.
Oct 11, 16:30 UTC
Resolved -
This incident has been resolved.
Oct 11, 14:19 UTC
Monitoring -
A fix has been implemented and we are monitoring the results.
Oct 11, 13:18 UTC
Investigating -
We are aware of an issue affecting the Grafana OnCall service in the prod-eu-west-0 region. Users may experience some slight performance degradation with alert ingestion and notifications.
Engineering is actively engaged and assessing the issue. We will provide updates accordingly.
Oct 11, 13:15 UTC