bgpreport

Network · data from 2026-11-12

AS39560 KT-NET Communications

Registry name: KT-NET KT-NET Communications GmbH, AT · PeeringDB

12IPv4 routes 0.0% RPKI valid · 100.0% with a route object
1IPv6 routes 0.0% RPKI valid · 100.0% with a route object
0RPKI invalid 0 origin · 0 maxLength
13No ROA 0 with no route object for this origin
0Low visibility seen by under 10% of full-table peers
0Route objects not announced registered with origin AS39560, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS39560, things to look at first. Visibility = full-table peers that see it, of 673 (IPv4) and 636 (IPv6) on 75 collectors. Also as routes.csv.

2.56.208.0/22 No ROA RIR databaseRIPE 673 100% 66
45.10.144.0/22 No ROA RIR databaseRIPE 673 100% 66
45.95.124.0/22 No ROA RIR databaseRIPE 673 100% 66
45.144.84.0/22 No ROA RIR databaseRIPE 673 100% 66
45.149.32.0/22 No ROA RIR databaseRIPE 673 100% 66
46.20.16.0/20 No ROA RIR databaseRIPE 673 100% 66
85.209.20.0/22 No ROA RIR databaseRIPE 673 100% 66
85.233.96.0/19 No ROA RIR databaseRIPE 673 100% 66
185.90.92.0/22 No ROA RIR databaseRIPE 673 100% 66
185.190.220.0/22 No ROA RIR databaseRIPE 673 100% 66
193.254.204.0/23 No ROA RIR databaseRIPE 673 100% 66
193.254.218.0/23 No ROA RIR databaseRIPE 673 100% 66
2a00:dc0::/32 No ROA RIR databaseRIPE 635 100% 69

AS-SET

PeeringDB's irr_as_set for AS39560: AS-KT-NET. Expanded from the day's IRR dumps the way bgpq4 does against whois.radb.net: a name with a database is read from that database only, one without from the first database in RADB's order. "Not covered" = this network's own routes that a filter built from the set would leave out (AS39560 isn't in the set, or no route object for AS39560 covers the route; more-specifics of a route object are accepted down to /24 and /48, as with bgpq4 -A -R 24 / -R 48). Customers' routes aren't counted: the collectors show each route's origin, not which network it came through.

NameDatabaseASNsSets Route objectsAS39560 in itNot covered
AS-KT-NET RIPE 2114 Yes 0

Fix list

The changes that would bring RPKI, the IRR and what's announced into line. Some are deliberate (a route object kept for a backup route, say); the network decides. All 13 are in fix.csv.

  • ROA: none13
ChangePrefix or setDetailFull-table peers
ROA: none2.56.208.0/22No ROA covers it. Add a ROA for AS39560, maxLength 22.673 of 673
ROA: none45.10.144.0/22No ROA covers it. Add a ROA for AS39560, maxLength 22.673 of 673
ROA: none45.95.124.0/22No ROA covers it. Add a ROA for AS39560, maxLength 22.673 of 673
ROA: none45.144.84.0/22No ROA covers it. Add a ROA for AS39560, maxLength 22.673 of 673
ROA: none45.149.32.0/22No ROA covers it. Add a ROA for AS39560, maxLength 22.673 of 673
ROA: none46.20.16.0/20No ROA covers it. Add a ROA for AS39560, maxLength 20.673 of 673
ROA: none85.209.20.0/22No ROA covers it. Add a ROA for AS39560, maxLength 22.673 of 673
ROA: none85.233.96.0/19No ROA covers it. Add a ROA for AS39560, maxLength 19.673 of 673
ROA: none185.90.92.0/22No ROA covers it. Add a ROA for AS39560, maxLength 22.673 of 673
ROA: none185.190.220.0/22No ROA covers it. Add a ROA for AS39560, maxLength 22.673 of 673
ROA: none193.254.204.0/23No ROA covers it. Add a ROA for AS39560, maxLength 23.673 of 673
ROA: none193.254.218.0/23No ROA covers it. Add a ROA for AS39560, maxLength 23.673 of 673
ROA: none2a00:dc0::/32No ROA covers it. Add a ROA for AS39560, maxLength 32.635 of 636

Route objects not announced

Every route object with origin AS39560 is announced.

Routes: the 08:00 UTC snapshots of 2026-11-12 from 75 RIPE RIS and RouteViews collectors. RPKI: our rpki-client run before the snapshot. IRR: the day's dumps of the five RIR databases and RADB's mirrors. The LEVEL3 and IDNIC databases publish no dump and aren't read, so route objects only there count as none.