bgpreport

Network · data from 2026-11-12

AS400941 NUBINITY

Registry name: NUBINITY - Nubinity, LLC, US · PeeringDB

11IPv4 routes 36.4% RPKI valid · 100.0% with a route object
5IPv6 routes 80.0% RPKI valid · 100.0% with a route object
0RPKI invalid 0 origin · 0 maxLength
8No ROA 0 with no route object for this origin
2Low visibility seen by under 10% of full-table peers
11Route objects not announced registered with origin AS400941, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS400941, 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.
38.2.152.0/22 No ROA Other IRR onlyRADB 673 100% 67
38.115.8.0/21 No ROA Other IRR onlyRADB 673 100% 67
38.183.220.0/22 No ROA Other IRR onlyRADB 673 100% 67
38.191.176.0/21 No ROA Other IRR onlyRADB 673 100% 67
38.225.200.0/22 No ROA Other IRR onlyRADB 673 100% 67
38.246.116.0/22 No ROA Other IRR onlyRADB 673 100% 67
38.211.195.0/24 No ROA Other IRR onlyRADB 672 100% 67
2a0e:b107:16e1::/48 No ROA RIR databaseRIPE 2 0%low visibility 2
38.115.32.0/21 Valid RIR databaseARIN 673 100% 67
38.115.40.0/23 Valid RIR databaseARIN 673 100% 67
38.115.42.0/23 Valid RIR databaseARIN 673 100% 67
38.115.44.0/22 Valid RIR databaseARIN 673 100% 67
2602:f66b:4::/48 Valid RIR databaseARIN 634 100% 69
2602:f66b:5::/48 Valid RIR databaseARIN 633 100% 67
2602:f66b:6::/48 Valid RIR databaseARIN 633 100% 67
2602:f66b:3::/48 Valid RIR databaseARIN 2 0%low visibility 2

AS-SET

AS400941's PeeringDB record names no AS-SET.

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

  • ROA: none8
  • Route object: RIR7
  • Route object: not announced11
ChangePrefix or setDetailFull-table peers
ROA: none38.2.152.0/22No ROA covers it. Add a ROA for AS400941, maxLength 22.673 of 673
Route object: RIR38.2.152.0/22Route object only in RADB. Add it in the RIR database for the space.673 of 673
ROA: none38.115.8.0/21No ROA covers it. Add a ROA for AS400941, maxLength 21.673 of 673
Route object: RIR38.115.8.0/21Route object only in RADB. Add it in the RIR database for the space.673 of 673
ROA: none38.183.220.0/22No ROA covers it. Add a ROA for AS400941, maxLength 22.673 of 673
Route object: RIR38.183.220.0/22Route object only in RADB. Add it in the RIR database for the space.673 of 673
ROA: none38.191.176.0/21No ROA covers it. Add a ROA for AS400941, maxLength 21.673 of 673
Route object: RIR38.191.176.0/21Route object only in RADB. Add it in the RIR database for the space.673 of 673
ROA: none38.225.200.0/22No ROA covers it. Add a ROA for AS400941, maxLength 22.673 of 673
Route object: RIR38.225.200.0/22Route object only in RADB. Add it in the RIR database for the space.673 of 673
ROA: none38.246.116.0/22No ROA covers it. Add a ROA for AS400941, maxLength 22.673 of 673
Route object: RIR38.246.116.0/22Route object only in RADB. Add it in the RIR database for the space.673 of 673
ROA: none38.211.195.0/24No ROA covers it. Add a ROA for AS400941, maxLength 24.672 of 673
Route object: RIR38.211.195.0/24Route object only in RADB. Add it in the RIR database for the space.672 of 673
ROA: none2a0e:b107:16e1::/48No ROA covers it. Add a ROA for AS400941, maxLength 48.2 of 636

Route objects not announced

Route objects with origin AS400941 whose prefix no peer sees AS400941 announce. Many are kept on purpose (backup routes, space announced only in some places).

38.2.240.0/20RADBNo ROA
38.115.32.0/20ARINValid
38.115.40.0/24ARINValid
38.115.41.0/24ARINValid
2602:f66b:1::/48ARINValid
2602:f66b:2::/48ARINValid
2602:f66b:fe::/48ARINValid
2a0e:46c4:1500::/44RIPENo ROA
2a0e:46c4:1508::/48RIPENo ROA
2a0e:b107:16e2::/48RIPENo ROA
2a0e:b107:16e3::/48RIPENo ROA

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.