bgpreport

Network · data from 2026-11-12

AS42908 Nordic Telecom

Registry name: CZ-NORDICTELECOMREGIONAL O2 Czech Republic, a.s., CZ · PeeringDB

35IPv4 routes 100.0% RPKI valid · 100.0% with a route object
9IPv6 routes 100.0% RPKI valid · 100.0% with a route object
0RPKI invalid 0 origin · 0 maxLength
0No 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 AS42908, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS42908, 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.
5.102.48.0/20 Valid RIR databaseRIPE 672 100% 67
31.10.56.0/21 Valid RIR databaseRIPE 672 100% 67
46.183.56.0/21 Valid RIR databaseRIPE 672 100% 67
46.231.72.0/21 Valid RIR databaseRIPE 672 100% 67
77.95.192.0/21 Valid RIR databaseRIPE 672 100% 67
78.136.128.0/18 Valid RIR databaseRIPE 672 100% 67
80.87.176.0/20 Valid RIR databaseRIPE 672 100% 67
80.90.128.0/20 Valid RIR databaseRIPE 672 100% 67
80.251.240.0/20 Valid RIR databaseRIPE 672 100% 67
88.81.64.0/19 Valid RIR databaseRIPE 672 100% 67
91.187.32.0/19 Valid RIR databaseRIPE 672 100% 67
92.61.80.0/20 Valid RIR databaseRIPE 672 100% 67
93.92.48.0/21 Valid RIR databaseRIPE 672 100% 67
93.93.32.0/21 Valid RIR databaseRIPE 672 100% 67
94.241.64.0/18 Valid RIR databaseRIPE 672 100% 67
109.108.96.0/19 Valid RIR databaseRIPE 672 100% 67
176.102.128.0/19 Valid RIR databaseRIPE 672 100% 67
178.17.80.0/20 Valid RIR databaseRIPE 672 100% 67
213.19.0.0/17 Valid RIR databaseRIPE 672 100% 67
213.155.32.0/19 Valid RIR databaseRIPE 672 100% 67
213.250.192.0/18 Valid RIR databaseRIPE 672 100% 67
217.170.96.0/20 Valid RIR databaseRIPE 672 100% 67
217.196.112.0/20 Valid RIR databaseRIPE 672 100% 67
217.197.144.0/20 Valid RIR databaseRIPE 672 100% 67
45.159.116.0/22 Valid RIR databaseRIPE 670 100% 67
80.78.136.0/22 Valid RIR databaseRIPE 670 100% 67
80.79.0.0/22 Valid RIR databaseRIPE 670 100% 67
80.243.236.0/22 Valid RIR databaseRIPE 670 100% 67
185.78.12.0/22 Valid RIR databaseRIPE 670 100% 67
185.82.236.0/22 Valid RIR databaseRIPE 670 100% 67
185.108.60.0/22 Valid RIR databaseRIPE 670 100% 67
185.157.240.0/22 Valid RIR databaseRIPE 670 100% 67
188.119.96.0/22 Valid RIR databaseRIPE 670 100% 67
193.42.128.0/22 Valid RIR databaseRIPE 670 100% 67
193.107.252.0/22 Valid RIR databaseRIPE 670 100% 67
2a00:e4c0::/32 Valid RIR databaseRIPE 635 100% 67
2a02:2428::/32 Valid RIR databaseRIPE 635 100% 67
2a03:1600::/32 Valid RIR databaseRIPE 635 100% 67
2a03:7a00::/32 Valid RIR databaseRIPE 635 100% 67
2a03:a820::/32 Valid RIR databaseRIPE 635 100% 67
2a01:9f40::/29 Valid RIR databaseRIPE 634 100% 67
2a02:2588::/29 Valid RIR databaseRIPE 634 100% 67
2a07:cc80::/29 Valid RIR databaseRIPE 634 100% 67
2a0c:8b40::/29 Valid RIR databaseRIPE 634 100% 67

AS-SET

PeeringDB's irr_as_set for AS42908: AS-NORDICTELECOM. 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 (AS42908 isn't in the set, or no route object for AS42908 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 objectsAS42908 in itNot covered
AS-NORDICTELECOM RIPE 5178 Yes 0

Fix list

Nothing to change: every route is RPKI valid with a route object in an RIR database, and every route object is announced.

Route objects not announced

Every route object with origin AS42908 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.