Independent automated monitoring of the Kurdistan Region's internet https://security.krd/ 2026-10-19T00:00:00Z tag:security.krd,2026:AUTO-2026-D4908E 2026-10-19T00:00:00Z 2026-10-19T00:00:00Z

background traffic reaching a darknet telescope dropped to critical: 6 observed against a normal level of 41. This measures whether the country's networks are reachable, not whether they are under attack — an outage and a cut cable look the same here. Seen 17 times between 2026-09-26T03:30 and 2026-10-19T01:50.

[CRITICAL] background traffic reaching a darknet telescope dropped to critical: 6 observed against a normal level of 41. This measures whether the country's networks are reachable, not whether they are under attack — an outage and a cut cable look the same here. Seen 17 times between 2026-09-26T03:30 and 2026-10-19T01:50. Affected: Entity: IQ. background traffic reaching a darknet telescope dropped to critical: 6 observed against a normal level of 41. This measures whether the country's networks are reachable, not whether they are under attack — an outage and a cut cable look the same here. Seen 17 times between 2026-09-26T03:30 and 2026-10-19T01:50. What to do now: - Confirm whether the named entity is yours or one of your suppliers. - If you do not understand a change, ask whoever runs the system before making it — your own provider or vendor, not this page. - Preserve logs covering the observation window. Drafted automatically from public sources. No person has reviewed it. Verify against the sources before acting. Machine-drafted from public sources; not reviewed by a person. tag:security.krd,2026:AUTO-2026-CD7520 2026-10-19T00:00:00Z 2026-10-19T00:00:00Z

background traffic reaching a darknet telescope dropped to critical: 8 observed against a normal level of 41. This measures whether the country's networks are reachable, not whether they are under attack — an outage and a cut cable look the same here. Seen 14 times between 2026-09-26T03:30 and 2026-10-19T00:54.

[CRITICAL] background traffic reaching a darknet telescope dropped to critical: 8 observed against a normal level of 41. This measures whether the country's networks are reachable, not whether they are under attack — an outage and a cut cable look the same here. Seen 14 times between 2026-09-26T03:30 and 2026-10-19T00:54. Affected: Entity: IQ. background traffic reaching a darknet telescope dropped to critical: 8 observed against a normal level of 41. This measures whether the country's networks are reachable, not whether they are under attack — an outage and a cut cable look the same here. Seen 14 times between 2026-09-26T03:30 and 2026-10-19T00:54. What to do now: - Confirm whether the named entity is yours or one of your suppliers. - If you do not understand a change, ask whoever runs the system before making it — your own provider or vendor, not this page. - Preserve logs covering the observation window. Drafted automatically from public sources. No person has reviewed it. Verify against the sources before acting. Machine-drafted from public sources; not reviewed by a person. tag:security.krd,2026:AUTO-2026-55F633 2026-10-19T00:00:00Z 2026-10-19T00:00:00Z

background traffic reaching a darknet telescope dropped to critical: 9 observed against a normal level of 41. This measures whether the country's networks are reachable, not whether they are under attack — an outage and a cut cable look the same here. Seen 20 times between 2026-09-26T03:30 and 2026-10-19T03:15.

[CRITICAL] background traffic reaching a darknet telescope dropped to critical: 9 observed against a normal level of 41. This measures whether the country's networks are reachable, not whether they are under attack — an outage and a cut cable look the same here. Seen 20 times between 2026-09-26T03:30 and 2026-10-19T03:15. Affected: Entity: IQ. background traffic reaching a darknet telescope dropped to critical: 9 observed against a normal level of 41. This measures whether the country's networks are reachable, not whether they are under attack — an outage and a cut cable look the same here. Seen 20 times between 2026-09-26T03:30 and 2026-10-19T03:15. What to do now: - Confirm whether the named entity is yours or one of your suppliers. - If you do not understand a change, ask whoever runs the system before making it — your own provider or vendor, not this page. - Preserve logs covering the observation window. Drafted automatically from public sources. No person has reviewed it. Verify against the sources before acting. Machine-drafted from public sources; not reviewed by a person. tag:security.krd,2026:AUTO-2026-11C7FA 2026-10-19T00:00:00Z 2026-10-19T00:00:00Z

background traffic reaching a darknet telescope dropped to critical: 7 observed against a normal level of 41. This measures whether the country's networks are reachable, not whether they are under attack — an outage and a cut cable look the same here. Seen 18 times between 2026-09-26T03:30 and 2026-10-19T02:18.

[CRITICAL] background traffic reaching a darknet telescope dropped to critical: 7 observed against a normal level of 41. This measures whether the country's networks are reachable, not whether they are under attack — an outage and a cut cable look the same here. Seen 18 times between 2026-09-26T03:30 and 2026-10-19T02:18. Affected: Entity: IQ. background traffic reaching a darknet telescope dropped to critical: 7 observed against a normal level of 41. This measures whether the country's networks are reachable, not whether they are under attack — an outage and a cut cable look the same here. Seen 18 times between 2026-09-26T03:30 and 2026-10-19T02:18. What to do now: - Confirm whether the named entity is yours or one of your suppliers. - If you do not understand a change, ask whoever runs the system before making it — your own provider or vendor, not this page. - Preserve logs covering the observation window. Drafted automatically from public sources. No person has reviewed it. Verify against the sources before acting. Machine-drafted from public sources; not reviewed by a person. tag:security.krd,2026:AUTO-2026-9D93DB 2026-10-18T00:00:00Z 2026-10-18T00:00:00Z

background traffic reaching a darknet telescope dropped to critical: 7 observed against a normal level of 45. This measures whether the country's networks are reachable, not whether they are under attack — an outage and a cut cable look the same here. Seen 13 times between 2026-09-26T03:30 and 2026-10-18T04:05.

[CRITICAL] background traffic reaching a darknet telescope dropped to critical: 7 observed against a normal level of 45. This measures whether the country's networks are reachable, not whether they are under attack — an outage and a cut cable look the same here. Seen 13 times between 2026-09-26T03:30 and 2026-10-18T04:05. Affected: Entity: IQ. background traffic reaching a darknet telescope dropped to critical: 7 observed against a normal level of 45. This measures whether the country's networks are reachable, not whether they are under attack — an outage and a cut cable look the same here. Seen 13 times between 2026-09-26T03:30 and 2026-10-18T04:05. What to do now: - Confirm whether the named entity is yours or one of your suppliers. - If you do not understand a change, ask whoever runs the system before making it — your own provider or vendor, not this page. - Preserve logs covering the observation window. Drafted automatically from public sources. No person has reviewed it. Verify against the sources before acting. Machine-drafted from public sources; not reviewed by a person. tag:security.krd,2026:AUTO-2026-2E7CAC 2026-10-16T00:00:00Z 2026-10-16T00:00:00Z

FortiOS, FortiPAM, FortiProxy, and FortiSwitchManager contain a path traversal vulnerability that may allow an authenticated attacker with admin profile and at least read-write permissions to write or delete arbitrary files via specific CLI commands. Listed by CISA as exploited in the wild, and the affected class of device terminates traffic at the perimeter.

[CRITICAL] FortiOS, FortiPAM, FortiProxy, and FortiSwitchManager contain a path traversal vulnerability that may allow an authenticated attacker with admin profile and at least read-write permissions to write or delete arbitrary files via specific CLI commands. Listed by CISA as exploited in the wild, and the affected class of device terminates traffic at the perimeter. Affected: Any internet-facing instance of the affected product. FortiOS, FortiPAM, FortiProxy, and FortiSwitchManager contain a path traversal vulnerability that may allow an authenticated attacker with admin profile and at least read-write permissions to write or delete arbitrary files via specific CLI commands. Listed by CISA as exploited in the wild, and the affected class of device terminates traffic at the perimeter. What to do now: - Patch now, or remove the device from the internet until you can. - Assume compromise on any unpatched internet-facing unit; patching does not evict an attacker already inside. - Rotate every credential and certificate the device held. - Review authentication logs from the vendor's fix date onward. Drafted automatically from public sources. No person has reviewed it. Verify against the sources before acting. Machine-drafted from public sources; not reviewed by a person. tag:security.krd,2026:AUTO-2026-13BEE1 2026-10-16T00:00:00Z 2026-10-16T00:00:00Z

Routing-status observations show networks registered as routed that announce no space, or that have one or two visible BGP neighbours. Single-upstream networks fail completely when that upstream does.

[HIGH] Routing-status observations show networks registered as routed that announce no space, or that have one or two visible BGP neighbours. Single-upstream networks fail completely when that upstream does. Affected: Regional autonomous systems listed in the evidence. Routing-status observations show networks registered as routed that announce no space, or that have one or two visible BGP neighbours. Single-upstream networks fail completely when that upstream does. What to do now: - Confirm whether your network appears below. - Establish a second transit or peering relationship; one upstream is not a network, it is a dependency. - Publish ROAs for every prefix you announce. - Ask your upstream what their own path diversity looks like. Drafted automatically from public sources. No person has reviewed it. Verify against the sources before acting. Machine-drafted from public sources; not reviewed by a person. tag:security.krd,2026:AUTO-2026-75E193 2026-10-14T00:00:00Z 2026-10-14T00:00:00Z

Cisco Secure Email Gateway contains a relative path traversal vulnerability that could allow an unauthenticated, remote attacker to write arbitrary files on the underlying operating system. Listed by CISA as exploited in the wild, and the affected class of device terminates traffic at the perimeter.

[CRITICAL] Cisco Secure Email Gateway contains a relative path traversal vulnerability that could allow an unauthenticated, remote attacker to write arbitrary files on the underlying operating system. Listed by CISA as exploited in the wild, and the affected class of device terminates traffic at the perimeter. Affected: Any internet-facing instance of the affected product. Cisco Secure Email Gateway contains a relative path traversal vulnerability that could allow an unauthenticated, remote attacker to write arbitrary files on the underlying operating system. Listed by CISA as exploited in the wild, and the affected class of device terminates traffic at the perimeter. What to do now: - Patch now, or remove the device from the internet until you can. - Assume compromise on any unpatched internet-facing unit; patching does not evict an attacker already inside. - Rotate every credential and certificate the device held. - Review authentication logs from the vendor's fix date onward. Drafted automatically from public sources. No person has reviewed it. Verify against the sources before acting. Machine-drafted from public sources; not reviewed by a person. tag:security.krd,2026:AUTO-2026-952D04 2026-10-13T00:00:00Z 2026-10-13T00:00:00Z

Ivanti Connect Secure contains an authentication bypass by spoofing vulnerability that allows a remote unauthenticated attacker to execute arbitrary commands. Listed by CISA as exploited in the wild, and the affected class of device terminates traffic at the perimeter.

[CRITICAL] Ivanti Connect Secure contains an authentication bypass by spoofing vulnerability that allows a remote unauthenticated attacker to execute arbitrary commands. Listed by CISA as exploited in the wild, and the affected class of device terminates traffic at the perimeter. Affected: Any internet-facing instance of the affected product. Ivanti Connect Secure contains an authentication bypass by spoofing vulnerability that allows a remote unauthenticated attacker to execute arbitrary commands. Listed by CISA as exploited in the wild, and the affected class of device terminates traffic at the perimeter. What to do now: - Patch now, or remove the device from the internet until you can. - Assume compromise on any unpatched internet-facing unit; patching does not evict an attacker already inside. - Rotate every credential and certificate the device held. - Review authentication logs from the vendor's fix date onward. Drafted automatically from public sources. No person has reviewed it. Verify against the sources before acting. Machine-drafted from public sources; not reviewed by a person. tag:security.krd,2026:AUTO-2026-3B68F3 2026-10-12T00:00:00Z 2026-10-12T00:00:00Z

Routing-status observations show networks registered as routed that announce no space, or that have one or two visible BGP neighbours. Single-upstream networks fail completely when that upstream does.

[HIGH] Routing-status observations show networks registered as routed that announce no space, or that have one or two visible BGP neighbours. Single-upstream networks fail completely when that upstream does. Affected: Regional autonomous systems listed in the evidence. Routing-status observations show networks registered as routed that announce no space, or that have one or two visible BGP neighbours. Single-upstream networks fail completely when that upstream does. What to do now: - Confirm whether your network appears below. - Establish a second transit or peering relationship; one upstream is not a network, it is a dependency. - Publish ROAs for every prefix you announce. - Ask your upstream what their own path diversity looks like. Drafted automatically from public sources. No person has reviewed it. Verify against the sources before acting. Machine-drafted from public sources; not reviewed by a person. tag:security.krd,2026:AUTO-2026-E1F4DD 2026-10-10T00:00:00Z 2026-10-10T00:00:00Z

BGP routing visibility dropped to critical: 3090 observed against a normal level of 3144. This measures whether the country's networks are reachable, not whether they are under attack — an outage and a cut cable look the same here. Seen 9 times between 2026-09-10T03:37 and 2026-10-08T03:30.

[CRITICAL] BGP routing visibility dropped to critical: 3090 observed against a normal level of 3144. This measures whether the country's networks are reachable, not whether they are under attack — an outage and a cut cable look the same here. Seen 9 times between 2026-09-10T03:37 and 2026-10-08T03:30. Affected: Entity: IQ. BGP routing visibility dropped to critical: 3090 observed against a normal level of 3144. This measures whether the country's networks are reachable, not whether they are under attack — an outage and a cut cable look the same here. Seen 9 times between 2026-09-10T03:37 and 2026-10-08T03:30. What to do now: - Confirm whether the named entity is yours or one of your suppliers. - If you do not understand a change, ask whoever runs the system before making it — your own provider or vendor, not this page. - Preserve logs covering the observation window. Drafted automatically from public sources. No person has reviewed it. Verify against the sources before acting. Machine-drafted from public sources; not reviewed by a person. tag:security.krd,2026:AUTO-2026-A07767 2026-10-10T00:00:00Z 2026-10-10T00:00:00Z

BGP routing visibility dropped to critical: 3090 observed against a normal level of 3144. This measures whether the country's networks are reachable, not whether they are under attack — an outage and a cut cable look the same here. Seen 8 times between 2026-09-26T03:30 and 2026-10-08T03:30.

[CRITICAL] BGP routing visibility dropped to critical: 3090 observed against a normal level of 3144. This measures whether the country's networks are reachable, not whether they are under attack — an outage and a cut cable look the same here. Seen 8 times between 2026-09-26T03:30 and 2026-10-08T03:30. Affected: Entity: IQ. BGP routing visibility dropped to critical: 3090 observed against a normal level of 3144. This measures whether the country's networks are reachable, not whether they are under attack — an outage and a cut cable look the same here. Seen 8 times between 2026-09-26T03:30 and 2026-10-08T03:30. What to do now: - Confirm whether the named entity is yours or one of your suppliers. - If you do not understand a change, ask whoever runs the system before making it — your own provider or vendor, not this page. - Preserve logs covering the observation window. Drafted automatically from public sources. No person has reviewed it. Verify against the sources before acting. Machine-drafted from public sources; not reviewed by a person. tag:security.krd,2026:AUTO-2026-A53972 2026-10-09T00:00:00Z 2026-10-09T00:00:00Z

BGP routing visibility dropped to critical: 3090 observed against a normal level of 3144. This measures whether the country's networks are reachable, not whether they are under attack — an outage and a cut cable look the same here. Seen 10 times between 2026-09-10T03:30 and 2026-10-08T03:30.

[CRITICAL] BGP routing visibility dropped to critical: 3090 observed against a normal level of 3144. This measures whether the country's networks are reachable, not whether they are under attack — an outage and a cut cable look the same here. Seen 10 times between 2026-09-10T03:30 and 2026-10-08T03:30. Affected: Entity: IQ. BGP routing visibility dropped to critical: 3090 observed against a normal level of 3144. This measures whether the country's networks are reachable, not whether they are under attack — an outage and a cut cable look the same here. Seen 10 times between 2026-09-10T03:30 and 2026-10-08T03:30. What to do now: - Confirm whether the named entity is yours or one of your suppliers. - If you do not understand a change, ask whoever runs the system before making it — your own provider or vendor, not this page. - Preserve logs covering the observation window. Drafted automatically from public sources. No person has reviewed it. Verify against the sources before acting. Machine-drafted from public sources; not reviewed by a person. tag:security.krd,2026:AUTO-2026-B4F996 2026-10-08T00:00:00Z 2026-10-08T00:00:00Z

BGP routing visibility dropped to critical: 3090 observed against a normal level of 3144. This measures whether the country's networks are reachable, not whether they are under attack — an outage and a cut cable look the same here. Seen 12 times between 2026-09-09T03:29 and 2026-10-08T03:30.

[CRITICAL] BGP routing visibility dropped to critical: 3090 observed against a normal level of 3144. This measures whether the country's networks are reachable, not whether they are under attack — an outage and a cut cable look the same here. Seen 12 times between 2026-09-09T03:29 and 2026-10-08T03:30. Affected: Entity: IQ. BGP routing visibility dropped to critical: 3090 observed against a normal level of 3144. This measures whether the country's networks are reachable, not whether they are under attack — an outage and a cut cable look the same here. Seen 12 times between 2026-09-09T03:29 and 2026-10-08T03:30. What to do now: - Confirm whether the named entity is yours or one of your suppliers. - If you do not understand a change, ask whoever runs the system before making it — your own provider or vendor, not this page. - Preserve logs covering the observation window. Drafted automatically from public sources. No person has reviewed it. Verify against the sources before acting. Machine-drafted from public sources; not reviewed by a person. tag:security.krd,2026:AUTO-2026-280EE0 2026-10-08T00:00:00Z 2026-10-08T00:00:00Z

active probing of regional address space dropped to critical: 300 observed against a normal level of 853. This measures whether the country's networks are reachable, not whether they are under attack — an outage and a cut cable look the same here. Seen 11 times between 2026-09-09T03:29 and 2026-10-06T03:30.

[CRITICAL] active probing of regional address space dropped to critical: 300 observed against a normal level of 853. This measures whether the country's networks are reachable, not whether they are under attack — an outage and a cut cable look the same here. Seen 11 times between 2026-09-09T03:29 and 2026-10-06T03:30. Affected: Entity: IQ. active probing of regional address space dropped to critical: 300 observed against a normal level of 853. This measures whether the country's networks are reachable, not whether they are under attack — an outage and a cut cable look the same here. Seen 11 times between 2026-09-09T03:29 and 2026-10-06T03:30. What to do now: - Confirm whether the named entity is yours or one of your suppliers. - If you do not understand a change, ask whoever runs the system before making it — your own provider or vendor, not this page. - Preserve logs covering the observation window. Drafted automatically from public sources. No person has reviewed it. Verify against the sources before acting. Machine-drafted from public sources; not reviewed by a person. tag:security.krd,2026:AUTO-2026-F16219 2026-10-07T00:00:00Z 2026-10-07T00:00:00Z

Routing-status observations show networks registered as routed that announce no space, or that have one or two visible BGP neighbours. Single-upstream networks fail completely when that upstream does.

[HIGH] Routing-status observations show networks registered as routed that announce no space, or that have one or two visible BGP neighbours. Single-upstream networks fail completely when that upstream does. Affected: Regional autonomous systems listed in the evidence. Routing-status observations show networks registered as routed that announce no space, or that have one or two visible BGP neighbours. Single-upstream networks fail completely when that upstream does. What to do now: - Confirm whether your network appears below. - Establish a second transit or peering relationship; one upstream is not a network, it is a dependency. - Publish ROAs for every prefix you announce. - Ask your upstream what their own path diversity looks like. Drafted automatically from public sources. No person has reviewed it. Verify against the sources before acting. Machine-drafted from public sources; not reviewed by a person. tag:security.krd,2026:AUTO-2026-89F8B4 2026-10-07T00:00:00Z 2026-10-07T00:00:00Z

Routing-status observations show networks registered as routed that announce no space, or that have one or two visible BGP neighbours. Single-upstream networks fail completely when that upstream does.

[HIGH] Routing-status observations show networks registered as routed that announce no space, or that have one or two visible BGP neighbours. Single-upstream networks fail completely when that upstream does. Affected: Regional autonomous systems listed in the evidence. Routing-status observations show networks registered as routed that announce no space, or that have one or two visible BGP neighbours. Single-upstream networks fail completely when that upstream does. What to do now: - Confirm whether your network appears below. - Establish a second transit or peering relationship; one upstream is not a network, it is a dependency. - Publish ROAs for every prefix you announce. - Ask your upstream what their own path diversity looks like. Drafted automatically from public sources. No person has reviewed it. Verify against the sources before acting. Machine-drafted from public sources; not reviewed by a person. tag:security.krd,2026:AUTO-2026-ED38BA 2026-10-05T00:00:00Z 2026-10-05T00:00:00Z

Routing-status observations show networks registered as routed that announce no space, or that have one or two visible BGP neighbours. Single-upstream networks fail completely when that upstream does.

[HIGH] Routing-status observations show networks registered as routed that announce no space, or that have one or two visible BGP neighbours. Single-upstream networks fail completely when that upstream does. Affected: Regional autonomous systems listed in the evidence. Routing-status observations show networks registered as routed that announce no space, or that have one or two visible BGP neighbours. Single-upstream networks fail completely when that upstream does. What to do now: - Confirm whether your network appears below. - Establish a second transit or peering relationship; one upstream is not a network, it is a dependency. - Publish ROAs for every prefix you announce. - Ask your upstream what their own path diversity looks like. Drafted automatically from public sources. No person has reviewed it. Verify against the sources before acting. Machine-drafted from public sources; not reviewed by a person. tag:security.krd,2026:AUTO-2026-D963C2 2026-10-05T00:00:00Z 2026-10-05T00:00:00Z

Routing-status observations show networks registered as routed that announce no space, or that have one or two visible BGP neighbours. Single-upstream networks fail completely when that upstream does.

[HIGH] Routing-status observations show networks registered as routed that announce no space, or that have one or two visible BGP neighbours. Single-upstream networks fail completely when that upstream does. Affected: Regional autonomous systems listed in the evidence. Routing-status observations show networks registered as routed that announce no space, or that have one or two visible BGP neighbours. Single-upstream networks fail completely when that upstream does. What to do now: - Confirm whether your network appears below. - Establish a second transit or peering relationship; one upstream is not a network, it is a dependency. - Publish ROAs for every prefix you announce. - Ask your upstream what their own path diversity looks like. Drafted automatically from public sources. No person has reviewed it. Verify against the sources before acting. Machine-drafted from public sources; not reviewed by a person. tag:security.krd,2026:AUTO-2026-3E51B3 2026-10-02T00:00:00Z 2026-10-02T00:00:00Z

Routing-status observations show networks registered as routed that announce no space, or that have one or two visible BGP neighbours. Single-upstream networks fail completely when that upstream does.

[HIGH] Routing-status observations show networks registered as routed that announce no space, or that have one or two visible BGP neighbours. Single-upstream networks fail completely when that upstream does. Affected: Regional autonomous systems listed in the evidence. Routing-status observations show networks registered as routed that announce no space, or that have one or two visible BGP neighbours. Single-upstream networks fail completely when that upstream does. What to do now: - Confirm whether your network appears below. - Establish a second transit or peering relationship; one upstream is not a network, it is a dependency. - Publish ROAs for every prefix you announce. - Ask your upstream what their own path diversity looks like. Drafted automatically from public sources. No person has reviewed it. Verify against the sources before acting. Machine-drafted from public sources; not reviewed by a person. tag:security.krd,2026:AUTO-2026-516203 2026-10-01T00:00:00Z 2026-10-01T00:00:00Z

Fortinet FortiMail contains a path traversal and an improper neutralization of NULL byte or NULL character vulnerability that may allow an unauthenticated attacker to write arbitrary files on the underlying system via crafted HTTP or HTTPS requests. Listed by CISA as exploited in the wild, and the affected class of device terminates traffic at the perimeter.

[CRITICAL] Fortinet FortiMail contains a path traversal and an improper neutralization of NULL byte or NULL character vulnerability that may allow an unauthenticated attacker to write arbitrary files on the underlying system via crafted HTTP or HTTPS requests. Listed by CISA as exploited in the wild, and the affected class of device terminates traffic at the perimeter. Affected: Any internet-facing instance of the affected product. Fortinet FortiMail contains a path traversal and an improper neutralization of NULL byte or NULL character vulnerability that may allow an unauthenticated attacker to write arbitrary files on the underlying system via crafted HTTP or HTTPS requests. Listed by CISA as exploited in the wild, and the affected class of device terminates traffic at the perimeter. What to do now: - Patch now, or remove the device from the internet until you can. - Assume compromise on any unpatched internet-facing unit; patching does not evict an attacker already inside. - Rotate every credential and certificate the device held. - Review authentication logs from the vendor's fix date onward. Drafted automatically from public sources. No person has reviewed it. Verify against the sources before acting. Machine-drafted from public sources; not reviewed by a person. tag:security.krd,2026:AUTO-2026-480DAE 2026-10-01T00:00:00Z 2026-10-01T00:00:00Z

Routing-status observations show networks registered as routed that announce no space, or that have one or two visible BGP neighbours. Single-upstream networks fail completely when that upstream does.

[HIGH] Routing-status observations show networks registered as routed that announce no space, or that have one or two visible BGP neighbours. Single-upstream networks fail completely when that upstream does. Affected: Regional autonomous systems listed in the evidence. Routing-status observations show networks registered as routed that announce no space, or that have one or two visible BGP neighbours. Single-upstream networks fail completely when that upstream does. What to do now: - Confirm whether your network appears below. - Establish a second transit or peering relationship; one upstream is not a network, it is a dependency. - Publish ROAs for every prefix you announce. - Ask your upstream what their own path diversity looks like. Drafted automatically from public sources. No person has reviewed it. Verify against the sources before acting. Machine-drafted from public sources; not reviewed by a person. tag:security.krd,2026:AUTO-2026-FBB11A 2026-09-29T00:00:00Z 2026-09-29T00:00:00Z

Routing-status observations show networks registered as routed that announce no space, or that have one or two visible BGP neighbours. Single-upstream networks fail completely when that upstream does.

[HIGH] Routing-status observations show networks registered as routed that announce no space, or that have one or two visible BGP neighbours. Single-upstream networks fail completely when that upstream does. Affected: Regional autonomous systems listed in the evidence. Routing-status observations show networks registered as routed that announce no space, or that have one or two visible BGP neighbours. Single-upstream networks fail completely when that upstream does. What to do now: - Confirm whether your network appears below. - Establish a second transit or peering relationship; one upstream is not a network, it is a dependency. - Publish ROAs for every prefix you announce. - Ask your upstream what their own path diversity looks like. Drafted automatically from public sources. No person has reviewed it. Verify against the sources before acting. Machine-drafted from public sources; not reviewed by a person. tag:security.krd,2026:AUTO-2026-DE0842 2026-09-28T00:00:00Z 2026-09-28T00:00:00Z

background traffic reaching a darknet telescope dropped to critical: 6 observed against a normal level of 34. This measures whether the country's networks are reachable, not whether they are under attack — an outage and a cut cable look the same here. Seen 23 times between 2026-08-30T03:30 and 2026-09-28T03:33.

[CRITICAL] background traffic reaching a darknet telescope dropped to critical: 6 observed against a normal level of 34. This measures whether the country's networks are reachable, not whether they are under attack — an outage and a cut cable look the same here. Seen 23 times between 2026-08-30T03:30 and 2026-09-28T03:33. Affected: Entity: IQ. background traffic reaching a darknet telescope dropped to critical: 6 observed against a normal level of 34. This measures whether the country's networks are reachable, not whether they are under attack — an outage and a cut cable look the same here. Seen 23 times between 2026-08-30T03:30 and 2026-09-28T03:33. What to do now: - Confirm whether the named entity is yours or one of your suppliers. - If you do not understand a change, ask whoever runs the system before making it — your own provider or vendor, not this page. - Preserve logs covering the observation window. Drafted automatically from public sources. No person has reviewed it. Verify against the sources before acting. Machine-drafted from public sources; not reviewed by a person. tag:security.krd,2026:AUTO-2026-D9C7D8 2026-09-27T00:00:00Z 2026-09-27T00:00:00Z

Citrix NetScaler ADC and NetScaler Gateway contain an improper restriction of operations within the bounds of a memory buffer vulnerability that could allow for remote code execution or denial of service Listed by CISA as exploited in the wild, and the affected class of device terminates traffic at the perimeter.

[CRITICAL] Citrix NetScaler ADC and NetScaler Gateway contain an improper restriction of operations within the bounds of a memory buffer vulnerability that could allow for remote code execution or denial of service Listed by CISA as exploited in the wild, and the affected class of device terminates traffic at the perimeter. Affected: Any internet-facing instance of the affected product. Citrix NetScaler ADC and NetScaler Gateway contain an improper restriction of operations within the bounds of a memory buffer vulnerability that could allow for remote code execution or denial of service Listed by CISA as exploited in the wild, and the affected class of device terminates traffic at the perimeter. What to do now: - Patch now, or remove the device from the internet until you can. - Assume compromise on any unpatched internet-facing unit; patching does not evict an attacker already inside. - Rotate every credential and certificate the device held. - Review authentication logs from the vendor's fix date onward. Drafted automatically from public sources. No person has reviewed it. Verify against the sources before acting. Machine-drafted from public sources; not reviewed by a person. tag:security.krd,2026:AUTO-2026-8415D7 2026-09-27T00:00:00Z 2026-09-27T00:00:00Z

Routing-status observations show networks registered as routed that announce no space, or that have one or two visible BGP neighbours. Single-upstream networks fail completely when that upstream does.

[HIGH] Routing-status observations show networks registered as routed that announce no space, or that have one or two visible BGP neighbours. Single-upstream networks fail completely when that upstream does. Affected: Regional autonomous systems listed in the evidence. Routing-status observations show networks registered as routed that announce no space, or that have one or two visible BGP neighbours. Single-upstream networks fail completely when that upstream does. What to do now: - Confirm whether your network appears below. - Establish a second transit or peering relationship; one upstream is not a network, it is a dependency. - Publish ROAs for every prefix you announce. - Ask your upstream what their own path diversity looks like. Drafted automatically from public sources. No person has reviewed it. Verify against the sources before acting. Machine-drafted from public sources; not reviewed by a person. tag:security.krd,2026:AUTO-2026-678921 2026-09-27T00:00:00Z 2026-09-27T00:00:00Z

Citrix NetScaler ADC and NetScaler Gateway contain an improper input validation vulnerability that could allow an unauthenticated attacker to execute arbitrary commands. Listed by CISA as exploited in the wild, and the affected class of device terminates traffic at the perimeter.

[CRITICAL] Citrix NetScaler ADC and NetScaler Gateway contain an improper input validation vulnerability that could allow an unauthenticated attacker to execute arbitrary commands. Listed by CISA as exploited in the wild, and the affected class of device terminates traffic at the perimeter. Affected: Any internet-facing instance of the affected product. Citrix NetScaler ADC and NetScaler Gateway contain an improper input validation vulnerability that could allow an unauthenticated attacker to execute arbitrary commands. Listed by CISA as exploited in the wild, and the affected class of device terminates traffic at the perimeter. What to do now: - Patch now, or remove the device from the internet until you can. - Assume compromise on any unpatched internet-facing unit; patching does not evict an attacker already inside. - Rotate every credential and certificate the device held. - Review authentication logs from the vendor's fix date onward. Drafted automatically from public sources. No person has reviewed it. Verify against the sources before acting. Machine-drafted from public sources; not reviewed by a person. tag:security.krd,2026:AUTO-2026-D7F65E 2026-09-26T00:00:00Z 2026-09-26T00:00:00Z

Routing-status observations show networks registered as routed that announce no space, or that have one or two visible BGP neighbours. Single-upstream networks fail completely when that upstream does.

[HIGH] Routing-status observations show networks registered as routed that announce no space, or that have one or two visible BGP neighbours. Single-upstream networks fail completely when that upstream does. Affected: Regional autonomous systems listed in the evidence. Routing-status observations show networks registered as routed that announce no space, or that have one or two visible BGP neighbours. Single-upstream networks fail completely when that upstream does. What to do now: - Confirm whether your network appears below. - Establish a second transit or peering relationship; one upstream is not a network, it is a dependency. - Publish ROAs for every prefix you announce. - Ask your upstream what their own path diversity looks like. Drafted automatically from public sources. No person has reviewed it. Verify against the sources before acting. Machine-drafted from public sources; not reviewed by a person. tag:security.krd,2026:AUTO-2026-FDD591 2026-09-25T00:00:00Z 2026-09-25T00:00:00Z

Mikrotik RouterOS contains an improper enforcement of behavioral workflow vulnerability that could allow an unauthenticated client to open a session channel and send an exec request. This vulnerability can be chained to achieve unauthenticated exploitation of CVE-2026-86060. Listed by CISA as exploited in the wild, and the affected class of device terminates traffic at the perimeter.

[CRITICAL] Mikrotik RouterOS contains an improper enforcement of behavioral workflow vulnerability that could allow an unauthenticated client to open a session channel and send an exec request. This vulnerability can be chained to achieve unauthenticated exploitation of CVE-2026-86060. Listed by CISA as exploited in the wild, and the affected class of device terminates traffic at the perimeter. Affected: Any internet-facing instance of the affected product. Mikrotik RouterOS contains an improper enforcement of behavioral workflow vulnerability that could allow an unauthenticated client to open a session channel and send an exec request. This vulnerability can be chained to achieve unauthenticated exploitation of CVE-2026-86060. Listed by CISA as exploited in the wild, and the affected class of device terminates traffic at the perimeter. What to do now: - Patch now, or remove the device from the internet until you can. - Assume compromise on any unpatched internet-facing unit; patching does not evict an attacker already inside. - Rotate every credential and certificate the device held. - Review authentication logs from the vendor's fix date onward. Drafted automatically from public sources. No person has reviewed it. Verify against the sources before acting. Machine-drafted from public sources; not reviewed by a person. tag:security.krd,2026:AUTO-2026-FA2354 2026-09-25T00:00:00Z 2026-09-25T00:00:00Z

background traffic reaching a darknet telescope dropped to critical: 15 observed against a normal level of 73. This measures whether the country's networks are reachable, not whether they are under attack — an outage and a cut cable look the same here. Seen 6 times between 2026-09-07T03:30 and 2026-09-10T03:37.

[CRITICAL] background traffic reaching a darknet telescope dropped to critical: 15 observed against a normal level of 73. This measures whether the country's networks are reachable, not whether they are under attack — an outage and a cut cable look the same here. Seen 6 times between 2026-09-07T03:30 and 2026-09-10T03:37. Affected: Entity: IQ. background traffic reaching a darknet telescope dropped to critical: 15 observed against a normal level of 73. This measures whether the country's networks are reachable, not whether they are under attack — an outage and a cut cable look the same here. Seen 6 times between 2026-09-07T03:30 and 2026-09-10T03:37. What to do now: - Confirm whether the named entity is yours or one of your suppliers. - If you do not understand a change, ask whoever runs the system before making it — your own provider or vendor, not this page. - Preserve logs covering the observation window. Drafted automatically from public sources. No person has reviewed it. Verify against the sources before acting. Machine-drafted from public sources; not reviewed by a person. tag:security.krd,2026:AUTO-2026-60B6C2 2026-09-25T00:00:00Z 2026-09-25T00:00:00Z

background traffic reaching a darknet telescope dropped to critical: 15 observed against a normal level of 73. This measures whether the country's networks are reachable, not whether they are under attack — an outage and a cut cable look the same here. Seen 5 times between 2026-09-08T03:30 and 2026-09-10T03:37.

[CRITICAL] background traffic reaching a darknet telescope dropped to critical: 15 observed against a normal level of 73. This measures whether the country's networks are reachable, not whether they are under attack — an outage and a cut cable look the same here. Seen 5 times between 2026-09-08T03:30 and 2026-09-10T03:37. Affected: Entity: IQ. background traffic reaching a darknet telescope dropped to critical: 15 observed against a normal level of 73. This measures whether the country's networks are reachable, not whether they are under attack — an outage and a cut cable look the same here. Seen 5 times between 2026-09-08T03:30 and 2026-09-10T03:37. What to do now: - Confirm whether the named entity is yours or one of your suppliers. - If you do not understand a change, ask whoever runs the system before making it — your own provider or vendor, not this page. - Preserve logs covering the observation window. Drafted automatically from public sources. No person has reviewed it. Verify against the sources before acting. Machine-drafted from public sources; not reviewed by a person. tag:security.krd,2026:AUTO-2026-0643FB 2026-09-25T00:00:00Z 2026-09-25T00:00:00Z

Microsoft SharePoint contains a code injection vulnerability which could allow an authorized attacker to execute code over a network. Listed by CISA as exploited in the wild, and the affected class of device terminates traffic at the perimeter.

[CRITICAL] Microsoft SharePoint contains a code injection vulnerability which could allow an authorized attacker to execute code over a network. Listed by CISA as exploited in the wild, and the affected class of device terminates traffic at the perimeter. Affected: Any internet-facing instance of the affected product. Microsoft SharePoint contains a code injection vulnerability which could allow an authorized attacker to execute code over a network. Listed by CISA as exploited in the wild, and the affected class of device terminates traffic at the perimeter. What to do now: - Patch now, or remove the device from the internet until you can. - Assume compromise on any unpatched internet-facing unit; patching does not evict an attacker already inside. - Rotate every credential and certificate the device held. - Review authentication logs from the vendor's fix date onward. Drafted automatically from public sources. No person has reviewed it. Verify against the sources before acting. Machine-drafted from public sources; not reviewed by a person. tag:security.krd,2026:AUTO-2026-D720CF 2026-09-21T00:00:00Z 2026-09-21T00:00:00Z

Routing-status observations show networks registered as routed that announce no space, or that have one or two visible BGP neighbours. Single-upstream networks fail completely when that upstream does.

[HIGH] Routing-status observations show networks registered as routed that announce no space, or that have one or two visible BGP neighbours. Single-upstream networks fail completely when that upstream does. Affected: Regional autonomous systems listed in the evidence. Routing-status observations show networks registered as routed that announce no space, or that have one or two visible BGP neighbours. Single-upstream networks fail completely when that upstream does. What to do now: - Confirm whether your network appears below. - Establish a second transit or peering relationship; one upstream is not a network, it is a dependency. - Publish ROAs for every prefix you announce. - Ask your upstream what their own path diversity looks like. Drafted automatically from public sources. No person has reviewed it. Verify against the sources before acting. Machine-drafted from public sources; not reviewed by a person. tag:security.krd,2026:AUTO-2026-96064D 2026-09-21T00:00:00Z 2026-09-21T00:00:00Z

Routing-status observations show networks registered as routed that announce no space, or that have one or two visible BGP neighbours. Single-upstream networks fail completely when that upstream does.

[HIGH] Routing-status observations show networks registered as routed that announce no space, or that have one or two visible BGP neighbours. Single-upstream networks fail completely when that upstream does. Affected: Regional autonomous systems listed in the evidence. Routing-status observations show networks registered as routed that announce no space, or that have one or two visible BGP neighbours. Single-upstream networks fail completely when that upstream does. What to do now: - Confirm whether your network appears below. - Establish a second transit or peering relationship; one upstream is not a network, it is a dependency. - Publish ROAs for every prefix you announce. - Ask your upstream what their own path diversity looks like. Drafted automatically from public sources. No person has reviewed it. Verify against the sources before acting. Machine-drafted from public sources; not reviewed by a person. tag:security.krd,2026:AUTO-2026-7E4EC7 2026-09-21T00:00:00Z 2026-09-21T00:00:00Z

Routing-status observations show networks registered as routed that announce no space, or that have one or two visible BGP neighbours. Single-upstream networks fail completely when that upstream does.

[HIGH] Routing-status observations show networks registered as routed that announce no space, or that have one or two visible BGP neighbours. Single-upstream networks fail completely when that upstream does. Affected: Regional autonomous systems listed in the evidence. Routing-status observations show networks registered as routed that announce no space, or that have one or two visible BGP neighbours. Single-upstream networks fail completely when that upstream does. What to do now: - Confirm whether your network appears below. - Establish a second transit or peering relationship; one upstream is not a network, it is a dependency. - Publish ROAs for every prefix you announce. - Ask your upstream what their own path diversity looks like. Drafted automatically from public sources. No person has reviewed it. Verify against the sources before acting. Machine-drafted from public sources; not reviewed by a person. tag:security.krd,2026:AUTO-2026-7D65DE 2026-09-21T00:00:00Z 2026-09-21T00:00:00Z

Routing-status observations show networks registered as routed that announce no space, or that have one or two visible BGP neighbours. Single-upstream networks fail completely when that upstream does.

[HIGH] Routing-status observations show networks registered as routed that announce no space, or that have one or two visible BGP neighbours. Single-upstream networks fail completely when that upstream does. Affected: Regional autonomous systems listed in the evidence. Routing-status observations show networks registered as routed that announce no space, or that have one or two visible BGP neighbours. Single-upstream networks fail completely when that upstream does. What to do now: - Confirm whether your network appears below. - Establish a second transit or peering relationship; one upstream is not a network, it is a dependency. - Publish ROAs for every prefix you announce. - Ask your upstream what their own path diversity looks like. Drafted automatically from public sources. No person has reviewed it. Verify against the sources before acting. Machine-drafted from public sources; not reviewed by a person. tag:security.krd,2026:AUTO-2026-5E532A 2026-09-21T00:00:00Z 2026-09-21T00:00:00Z

Routing-status observations show networks registered as routed that announce no space, or that have one or two visible BGP neighbours. Single-upstream networks fail completely when that upstream does.

[HIGH] Routing-status observations show networks registered as routed that announce no space, or that have one or two visible BGP neighbours. Single-upstream networks fail completely when that upstream does. Affected: Regional autonomous systems listed in the evidence. Routing-status observations show networks registered as routed that announce no space, or that have one or two visible BGP neighbours. Single-upstream networks fail completely when that upstream does. What to do now: - Confirm whether your network appears below. - Establish a second transit or peering relationship; one upstream is not a network, it is a dependency. - Publish ROAs for every prefix you announce. - Ask your upstream what their own path diversity looks like. Drafted automatically from public sources. No person has reviewed it. Verify against the sources before acting. Machine-drafted from public sources; not reviewed by a person. tag:security.krd,2026:AUTO-2026-525B61 2026-09-21T00:00:00Z 2026-09-21T00:00:00Z

Routing-status observations show networks registered as routed that announce no space, or that have one or two visible BGP neighbours. Single-upstream networks fail completely when that upstream does.

[HIGH] Routing-status observations show networks registered as routed that announce no space, or that have one or two visible BGP neighbours. Single-upstream networks fail completely when that upstream does. Affected: Regional autonomous systems listed in the evidence. Routing-status observations show networks registered as routed that announce no space, or that have one or two visible BGP neighbours. Single-upstream networks fail completely when that upstream does. What to do now: - Confirm whether your network appears below. - Establish a second transit or peering relationship; one upstream is not a network, it is a dependency. - Publish ROAs for every prefix you announce. - Ask your upstream what their own path diversity looks like. Drafted automatically from public sources. No person has reviewed it. Verify against the sources before acting. Machine-drafted from public sources; not reviewed by a person. tag:security.krd,2026:AUTO-2026-4C6E35 2026-09-21T00:00:00Z 2026-09-21T00:00:00Z

Routing-status observations show networks registered as routed that announce no space, or that have one or two visible BGP neighbours. Single-upstream networks fail completely when that upstream does.

[HIGH] Routing-status observations show networks registered as routed that announce no space, or that have one or two visible BGP neighbours. Single-upstream networks fail completely when that upstream does. Affected: Regional autonomous systems listed in the evidence. Routing-status observations show networks registered as routed that announce no space, or that have one or two visible BGP neighbours. Single-upstream networks fail completely when that upstream does. What to do now: - Confirm whether your network appears below. - Establish a second transit or peering relationship; one upstream is not a network, it is a dependency. - Publish ROAs for every prefix you announce. - Ask your upstream what their own path diversity looks like. Drafted automatically from public sources. No person has reviewed it. Verify against the sources before acting. Machine-drafted from public sources; not reviewed by a person. tag:security.krd,2026:AUTO-2026-434B1D 2026-09-21T00:00:00Z 2026-09-21T00:00:00Z

Routing-status observations show networks registered as routed that announce no space, or that have one or two visible BGP neighbours. Single-upstream networks fail completely when that upstream does.

[HIGH] Routing-status observations show networks registered as routed that announce no space, or that have one or two visible BGP neighbours. Single-upstream networks fail completely when that upstream does. Affected: Regional autonomous systems listed in the evidence. Routing-status observations show networks registered as routed that announce no space, or that have one or two visible BGP neighbours. Single-upstream networks fail completely when that upstream does. What to do now: - Confirm whether your network appears below. - Establish a second transit or peering relationship; one upstream is not a network, it is a dependency. - Publish ROAs for every prefix you announce. - Ask your upstream what their own path diversity looks like. Drafted automatically from public sources. No person has reviewed it. Verify against the sources before acting. Machine-drafted from public sources; not reviewed by a person. tag:security.krd,2026:AUTO-2026-42A285 2026-09-21T00:00:00Z 2026-09-21T00:00:00Z

Routing-status observations show networks registered as routed that announce no space, or that have one or two visible BGP neighbours. Single-upstream networks fail completely when that upstream does.

[HIGH] Routing-status observations show networks registered as routed that announce no space, or that have one or two visible BGP neighbours. Single-upstream networks fail completely when that upstream does. Affected: Regional autonomous systems listed in the evidence. Routing-status observations show networks registered as routed that announce no space, or that have one or two visible BGP neighbours. Single-upstream networks fail completely when that upstream does. What to do now: - Confirm whether your network appears below. - Establish a second transit or peering relationship; one upstream is not a network, it is a dependency. - Publish ROAs for every prefix you announce. - Ask your upstream what their own path diversity looks like. Drafted automatically from public sources. No person has reviewed it. Verify against the sources before acting. Machine-drafted from public sources; not reviewed by a person. tag:security.krd,2026:AUTO-2026-3141C1 2026-09-21T00:00:00Z 2026-09-21T00:00:00Z

Zyxel GS1900 series switches contain a stack-based buffer overflow vulnerability in the CGI program which could allow a LAN-based, unauthenticated attacker to exploit the flaw and potentially execute OS commands via a crafted HTTP request. Listed by CISA as exploited in the wild, and the affected class of device terminates traffic at the perimeter.

[CRITICAL] Zyxel GS1900 series switches contain a stack-based buffer overflow vulnerability in the CGI program which could allow a LAN-based, unauthenticated attacker to exploit the flaw and potentially execute OS commands via a crafted HTTP request. Listed by CISA as exploited in the wild, and the affected class of device terminates traffic at the perimeter. Affected: Any internet-facing instance of the affected product. Zyxel GS1900 series switches contain a stack-based buffer overflow vulnerability in the CGI program which could allow a LAN-based, unauthenticated attacker to exploit the flaw and potentially execute OS commands via a crafted HTTP request. Listed by CISA as exploited in the wild, and the affected class of device terminates traffic at the perimeter. What to do now: - Patch now, or remove the device from the internet until you can. - Assume compromise on any unpatched internet-facing unit; patching does not evict an attacker already inside. - Rotate every credential and certificate the device held. - Review authentication logs from the vendor's fix date onward. Drafted automatically from public sources. No person has reviewed it. Verify against the sources before acting. Machine-drafted from public sources; not reviewed by a person. tag:security.krd,2026:AUTO-2026-263C71 2026-09-21T00:00:00Z 2026-09-21T00:00:00Z

Routing-status observations show networks registered as routed that announce no space, or that have one or two visible BGP neighbours. Single-upstream networks fail completely when that upstream does.

[HIGH] Routing-status observations show networks registered as routed that announce no space, or that have one or two visible BGP neighbours. Single-upstream networks fail completely when that upstream does. Affected: Regional autonomous systems listed in the evidence. Routing-status observations show networks registered as routed that announce no space, or that have one or two visible BGP neighbours. Single-upstream networks fail completely when that upstream does. What to do now: - Confirm whether your network appears below. - Establish a second transit or peering relationship; one upstream is not a network, it is a dependency. - Publish ROAs for every prefix you announce. - Ask your upstream what their own path diversity looks like. Drafted automatically from public sources. No person has reviewed it. Verify against the sources before acting. Machine-drafted from public sources; not reviewed by a person. tag:security.krd,2026:AUTO-2026-13A0D1 2026-09-21T00:00:00Z 2026-09-21T00:00:00Z

Routing-status observations show networks registered as routed that announce no space, or that have one or two visible BGP neighbours. Single-upstream networks fail completely when that upstream does.

[HIGH] Routing-status observations show networks registered as routed that announce no space, or that have one or two visible BGP neighbours. Single-upstream networks fail completely when that upstream does. Affected: Regional autonomous systems listed in the evidence. Routing-status observations show networks registered as routed that announce no space, or that have one or two visible BGP neighbours. Single-upstream networks fail completely when that upstream does. What to do now: - Confirm whether your network appears below. - Establish a second transit or peering relationship; one upstream is not a network, it is a dependency. - Publish ROAs for every prefix you announce. - Ask your upstream what their own path diversity looks like. Drafted automatically from public sources. No person has reviewed it. Verify against the sources before acting. Machine-drafted from public sources; not reviewed by a person. tag:security.krd,2026:AUTO-2026-E4CE34 2026-09-18T00:00:00Z 2026-09-18T00:00:00Z

Routing-status observations show networks registered as routed that announce no space, or that have one or two visible BGP neighbours. Single-upstream networks fail completely when that upstream does.

[HIGH] Routing-status observations show networks registered as routed that announce no space, or that have one or two visible BGP neighbours. Single-upstream networks fail completely when that upstream does. Affected: Regional autonomous systems listed in the evidence. Routing-status observations show networks registered as routed that announce no space, or that have one or two visible BGP neighbours. Single-upstream networks fail completely when that upstream does. What to do now: - Confirm whether your network appears below. - Establish a second transit or peering relationship; one upstream is not a network, it is a dependency. - Publish ROAs for every prefix you announce. - Ask your upstream what their own path diversity looks like. Drafted automatically from public sources. No person has reviewed it. Verify against the sources before acting. Machine-drafted from public sources; not reviewed by a person. tag:security.krd,2026:AUTO-2026-8C24D2 2026-09-18T00:00:00Z 2026-09-18T00:00:00Z

Routing-status observations show networks registered as routed that announce no space, or that have one or two visible BGP neighbours. Single-upstream networks fail completely when that upstream does.

[HIGH] Routing-status observations show networks registered as routed that announce no space, or that have one or two visible BGP neighbours. Single-upstream networks fail completely when that upstream does. Affected: Regional autonomous systems listed in the evidence. Routing-status observations show networks registered as routed that announce no space, or that have one or two visible BGP neighbours. Single-upstream networks fail completely when that upstream does. What to do now: - Confirm whether your network appears below. - Establish a second transit or peering relationship; one upstream is not a network, it is a dependency. - Publish ROAs for every prefix you announce. - Ask your upstream what their own path diversity looks like. Drafted automatically from public sources. No person has reviewed it. Verify against the sources before acting. Machine-drafted from public sources; not reviewed by a person. tag:security.krd,2026:AUTO-2026-549C85 2026-09-15T00:00:00Z 2026-09-15T00:00:00Z

Routing-status observations show networks registered as routed that announce no space, or that have one or two visible BGP neighbours. Single-upstream networks fail completely when that upstream does.

[HIGH] Routing-status observations show networks registered as routed that announce no space, or that have one or two visible BGP neighbours. Single-upstream networks fail completely when that upstream does. Affected: Regional autonomous systems listed in the evidence. Routing-status observations show networks registered as routed that announce no space, or that have one or two visible BGP neighbours. Single-upstream networks fail completely when that upstream does. What to do now: - Confirm whether your network appears below. - Establish a second transit or peering relationship; one upstream is not a network, it is a dependency. - Publish ROAs for every prefix you announce. - Ask your upstream what their own path diversity looks like. Drafted automatically from public sources. No person has reviewed it. Verify against the sources before acting. Machine-drafted from public sources; not reviewed by a person. tag:security.krd,2026:AUTO-2026-EF17EF 2026-09-14T00:00:00Z 2026-09-14T00:00:00Z

Routing-status observations show networks registered as routed that announce no space, or that have one or two visible BGP neighbours. Single-upstream networks fail completely when that upstream does.

[HIGH] Routing-status observations show networks registered as routed that announce no space, or that have one or two visible BGP neighbours. Single-upstream networks fail completely when that upstream does. Affected: Regional autonomous systems listed in the evidence. Routing-status observations show networks registered as routed that announce no space, or that have one or two visible BGP neighbours. Single-upstream networks fail completely when that upstream does. What to do now: - Confirm whether your network appears below. - Establish a second transit or peering relationship; one upstream is not a network, it is a dependency. - Publish ROAs for every prefix you announce. - Ask your upstream what their own path diversity looks like. Drafted automatically from public sources. No person has reviewed it. Verify against the sources before acting. Machine-drafted from public sources; not reviewed by a person. tag:security.krd,2026:AUTO-2026-EEC672 2026-09-14T00:00:00Z 2026-09-14T00:00:00Z

Cisco AsyncOS software for Cisco Secure Email Gateway (SEG) contains a SQL injection vulnerability that could allow an unauthenticated, remote attacker to execute arbitrary commands with root privileges on the underlying operating system. Listed by CISA as exploited in the wild, and the affected class of device terminates traffic at the perimeter.

[CRITICAL] Cisco AsyncOS software for Cisco Secure Email Gateway (SEG) contains a SQL injection vulnerability that could allow an unauthenticated, remote attacker to execute arbitrary commands with root privileges on the underlying operating system. Listed by CISA as exploited in the wild, and the affected class of device terminates traffic at the perimeter. Affected: Any internet-facing instance of the affected product. Cisco AsyncOS software for Cisco Secure Email Gateway (SEG) contains a SQL injection vulnerability that could allow an unauthenticated, remote attacker to execute arbitrary commands with root privileges on the underlying operating system. Listed by CISA as exploited in the wild, and the affected class of device terminates traffic at the perimeter. What to do now: - Patch now, or remove the device from the internet until you can. - Assume compromise on any unpatched internet-facing unit; patching does not evict an attacker already inside. - Rotate every credential and certificate the device held. - Review authentication logs from the vendor's fix date onward. Drafted automatically from public sources. No person has reviewed it. Verify against the sources before acting. Machine-drafted from public sources; not reviewed by a person. tag:security.krd,2026:AUTO-2026-D9ECE8 2026-09-14T00:00:00Z 2026-09-14T00:00:00Z

Routing-status observations show networks registered as routed that announce no space, or that have one or two visible BGP neighbours. Single-upstream networks fail completely when that upstream does.

[HIGH] Routing-status observations show networks registered as routed that announce no space, or that have one or two visible BGP neighbours. Single-upstream networks fail completely when that upstream does. Affected: Regional autonomous systems listed in the evidence. Routing-status observations show networks registered as routed that announce no space, or that have one or two visible BGP neighbours. Single-upstream networks fail completely when that upstream does. What to do now: - Confirm whether your network appears below. - Establish a second transit or peering relationship; one upstream is not a network, it is a dependency. - Publish ROAs for every prefix you announce. - Ask your upstream what their own path diversity looks like. Drafted automatically from public sources. No person has reviewed it. Verify against the sources before acting. Machine-drafted from public sources; not reviewed by a person.