bgpreport

Network · data from 2026-11-12

AS38016 Nokia IP Networks Labs

Registry name: NOK-IP-NET-LABS - Nokia IP Networks Labs, AU · PeeringDB

6IPv4 routes 16.7% RPKI valid · 16.7% with a route object
8IPv6 routes 37.5% RPKI valid · 37.5% with a route object
6RPKI invalid 6 origin · 0 maxLength
4No ROA 10 with no route object for this origin
10Low visibility seen by under 10% of full-table peers
0Route objects not announced registered with origin AS38016, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS38016, 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.

46.18.174.240/30 Invalid: origin None 1 0%low visibility 1
80.81.192.0/21 Invalid: origin None 1 0%low visibility 1
206.82.104.0/22 Invalid: origin None 1 0%low visibility 1
2001:504:36::/64 Invalid: origin None 1 0%low visibility 1
2001:7f8::/64 Invalid: origin None 1 0%low visibility 1
2a02:27f0:2:278::/64 Invalid: origin None 1 0%low visibility 1
0.0.0.0/0 bogon No ROA None 1 0%low visibility 1
192.0.2.1/32 bogon No ROA None 1 0%low visibility 1
::/0 bogon No ROA None 1 0%low visibility 1
2001:db8:0:dead:beef::1/128 bogon No ROA None 1 0%low visibility 1
135.92.55.0/24 Valid RIR databaseARIN 672 100% 66
2406:c800:a1ca::/48 Valid RIR databaseAPNIC 635 100% 69
2406:c800::/32 Valid RIR databaseAPNIC 634 100% 69
2406:c800:e000::/48 Valid RIR databaseAPNIC 634 100% 69

AS-SET

PeeringDB's irr_as_set for AS38016: AS38016. 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 (AS38016 isn't in the set, or no route object for AS38016 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 objectsAS38016 in itNot covered
AS38016 A single AS number, not a set: AS38016 (this network), 4 route objects.

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 16 are in fix.csv.

  • ROA: origin6
  • Bogon prefix4
  • Route object: none6
ChangePrefix or setDetailFull-table peers
ROA: origin46.18.174.240/30ROAs covering it name AS4455, AS31216, AS43531, not AS38016. If AS38016 should announce it, add a ROA for AS38016.1 of 673
Route object: none46.18.174.240/30No route object for it. Add a route object with origin AS38016 in the RIR database for the space.1 of 673
ROA: origin80.81.192.0/21An AS0 ROA covers it (the holder's statement that it shouldn't be routed). If AS38016 should announce it, add a ROA for AS38016.1 of 673
Route object: none80.81.192.0/21No route object for it. Add a route object with origin AS38016 in the RIR database for the space.1 of 673
ROA: origin206.82.104.0/22An AS0 ROA covers it (the holder's statement that it shouldn't be routed). If AS38016 should announce it, add a ROA for AS38016.1 of 673
Route object: none206.82.104.0/22No route object for it. Add a route object with origin AS38016 in the RIR database for the space.1 of 673
ROA: origin2001:504:36::/64An AS0 ROA covers it (the holder's statement that it shouldn't be routed). If AS38016 should announce it, add a ROA for AS38016.1 of 636
Route object: none2001:504:36::/64No route object for it. Add a route object with origin AS38016 in the RIR database for the space.1 of 636
ROA: origin2001:7f8::/64An AS0 ROA covers it (the holder's statement that it shouldn't be routed). If AS38016 should announce it, add a ROA for AS38016.1 of 636
Route object: none2001:7f8::/64No route object for it. Add a route object with origin AS38016 in the RIR database for the space.1 of 636
ROA: origin2a02:27f0:2:278::/64ROAs covering it name AS4455, AS31216, AS43531, not AS38016. If AS38016 should announce it, add a ROA for AS38016.1 of 636
Route object: none2a02:27f0:2:278::/64No route object for it. Add a route object with origin AS38016 in the RIR database for the space.1 of 636
Bogon prefix0.0.0.0/0In IANA's special-purpose registry: default route.1 of 673
Bogon prefix192.0.2.1/32In IANA's special-purpose registry: Documentation (TEST-NET-1) (RFC 5737).1 of 673
Bogon prefix::/0In IANA's special-purpose registry: default route.1 of 636
Bogon prefix2001:db8:0:dead:beef::1/128In IANA's special-purpose registry: Documentation (RFC 3849).1 of 636

Route objects not announced

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