Nov 8, 16:00:00 GMT+0
Monitoring -
There is an ongoing incident with our DNS provider (NS1) which is causing issues during provisioning of DNS entries for newly created services and addons.
https://ns1status.com/#!/incident/507854
Existing services and addons are not affected..
Nov 8, 17:01:01 GMT+0
Resolved -
This incident has been resolved..
Aug 4, 13:29:12 GMT+0
Investigating -
We are currently investigating intermittent networking connectivity issues. .
Aug 4, 14:09:40 GMT+0
Resolved -
This incident has been resolved..
Jun 16, 12:41:00 GMT+0
Identified -
Northflank's logging backend is experiencing performance and connectivity issues. We are investigating, and engineers are implementing a fix.
Users may see intermittent log query failures, and live tailing issues in the UI, CLI and API..
Jun 16, 14:21:00 GMT+0
Resolved -
This incident has been resolved..
May 11, 11:49:50 GMT+0
Identified -
Google’s Safe Browsing has marked *.code.run as a dangerous domain. This impacts all public HTTPS endpoints that do not use a custom domain. We recommend appealing for your specific service domains at [https://safebrowsing.google.com/safebrowsing/report_error/](https://safebrowsing.google.com/safebrowsing/report_error/).
We have sent the relevant documentation via Google Search Console and await a response from Google. We will explore options including:
- temporarily using another domain for new workloads
- exploring wildcard and vanity replacement of *.code.run on a per-user basis
- adding *.code.run to an allow-list
Cause:
A user was caught deploying a phishing website and was banned within 10 minutes of notification. *.code.run is a member of the PSL, and, unfortunately, it is not considered when blocking thousands of domains for one offending workload..
May 11, 13:11:15 GMT+0
Resolved -
It appears the warning has been lifted for *.code.run domains and are now working as expected. We continue to monitor the situation closely. We apologise for any inconvenience..
Jan 12, 11:56:47 GMT+0
Identified -
We have identified an issue with our DNS provider with delayed propagation of DNS entries. This is delaying custom domain certificate creation, new public code.run endpoints and addon creation. We are monitoring and will update when we have more updates..
Jan 12, 13:02:59 GMT+0
Resolved -
DNS is performing as expected, you can create domains and databases in a timely manor.
NS1 DNS incident has been resolved: https://ns1status.com/#!/incident/400072.
Nov 29, 19:32:44 GMT+0
Identified -
We have identified an issue with our DNS provider with delayed propagation of DNS entries. This is delaying custom domain certificate creation, new public code.run endpoints and addon creation. We are monitoring and will update when we have more updates..
Nov 29, 23:28:17 GMT+0
Monitoring -
NS1 continues to work on mitigations and a fix.
https://ns1status.com/#!/incident/390630.
Nov 30, 04:34:00 GMT+0
Resolved -
Our DNS provider has resolved the propagation issue.
https://ns1status.com/#!/incident/390630
Systems are operational..
Nov 17, 12:23:15 GMT+0
Investigating -
We are currently investigating this incident..
Nov 17, 12:55:31 GMT+0
Monitoring -
We implemented a fix and currently monitoring the result..
Nov 17, 13:29:54 GMT+0
Resolved -
The issue is now resolved. All logging and log sink ingestion is successfully being processed and doing so performantly..
Oct 13, 10:00:00 GMT+0
Resolved -
The issue was resolved..
Oct 13, 08:40:00 GMT+0
Investigating -
We are currently investigating this incident..
Oct 13, 09:30:00 GMT+0
Monitoring -
We implemented a fix and currently monitoring the result..
Aug 26, 15:34:56 GMT+0
Resolved -
Our DNS provider NS1 experienced a temporary DNS outage from 16:18:12 UTC until 16:20:00 UTC <-> 16:23:47 UTC. We will continue to monitor the situation
https://ns1status.com/#!/incident/367771.
Feb 2, 11:27:02 GMT+0
Identified -
Some users are experiencing delays in job, service, and addon scheduling. We have identified networking issues within Konnectivity agent and are working with GKE Engineering to resolve the situation. This was triggered by a routine Kubernetes upgrade..
Feb 2, 13:30:00 GMT+0
Resolved -
Northflank engineers have put a mitigation in place for connectivity issues affecting new workloads deployed with health checks. Workloads are operating as expected and we will continue to monitor the situation..
Oct 29, 12:10:00 GMT+0
Identified -
A rollout of our new CMS temporarily took our certificates offline, you may have experienced connection issues. This did not affect any of your workloads or public HTTP endpoints..
Oct 29, 12:15:00 GMT+0
Resolved -
This incident is now resolved..