bgpreport

Network · data from 2026-11-12

AS46997 Nato Internet Service

Registry name: NATOLAB - Black Mesa Corporation, US · PeeringDB

14IPv4 routes 92.9% RPKI valid · 100.0% with a route object
28IPv6 routes 32.1% RPKI valid · 46.4% with a route object
3RPKI invalid 1 origin · 2 maxLength
17No ROA 15 with no route object for this origin
6Low visibility seen by under 10% of full-table peers
18Route objects not announced registered with origin AS46997, seen from no peer

Announced routes

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

2001:df0:ac40::/48 Invalid: origin Other origin only 16 3%low visibility 13
2602:feda:31::/48 Invalid: maxLength Nonecovered by 2602:feda::/36 16 3%low visibility 13
2602:feda:32::/48 Invalid: maxLength Nonecovered by 2602:feda::/36 16 3%low visibility 13
2406:4440:40::/44 No ROA Other origin only 633 100% 69
2406:4440:d6ff::/48 No ROA Other origin only 633 100% 69
2602:feda:60::/44 No ROA Nonecovered by 2602:feda::/36 633 100% 68
2602:feda:f380::/44 No ROA Nonecovered by 2602:feda:f300::/40 633 100% 69
2602:feda:f390::/44 No ROA Nonecovered by 2602:feda:f300::/40 633 100% 69
2406:4440:f00::/40 No ROA None 27 4%low visibility 18
2602:feda:f105::/48 No ROA Nonecovered by 2602:feda:f100::/40 27 4%low visibility 18
2407:9240:2400::/40 No ROA None 22 3%low visibility 17
44.68.205.0/24 No ROA Other IRR onlyALTDB 669 99% 68
2602:feda:dd0::/44 No ROA Other IRR onlyALTDB 633 100% 69
2406:4440:20::/44 No ROA RIR databaseAPNIC 633 100% 68
2602:fd92:c20::/44 No ROA RIR databaseARIN 633 100% 69
2602:fd92:c20::/45 No ROA RIR databaseARIN 633 100% 69
2602:fd92:c28::/45 No ROA RIR databaseARIN 633 100% 69
2602:feda:f100::/40 No ROA RIR databaseARIN 633 100% 69
2602:feda:f200::/44 No ROA RIR databaseARIN 633 100% 69
2602:feda:f300::/40 No ROA RIR databaseARIN 633 100% 69
2602:feda:a3::/48 Valid Nonecovered by 2602:feda:a0::/44 635 100% 68
2602:feda:8::/48 Valid Nonecovered by 2602:feda::/36 634 100% 68
2602:feda:30::/44 Valid Nonecovered by 2602:feda::/36 633 100% 69
2602:feda:38::/45 Valid Nonecovered by 2602:feda::/36 633 100% 69
23.247.136.0/23 Valid Other IRR onlyALTDB 669 99% 68
23.247.136.0/24 Valid Other IRR onlyALTDB 669 99% 68
23.247.137.0/24 Valid Other IRR onlyALTDB 669 99% 68
103.175.98.0/24 Valid RIR databaseAPNIC 671 100% 67
103.186.163.0/24 Valid RIR databaseAPNIC 671 100% 67
134.195.100.0/24 Valid RIR databaseARIN 671 100% 67
103.152.112.0/23 Valid RIR databaseAPNIC 669 99% 68
103.152.112.0/24 Valid RIR databaseAPNIC 669 99% 68
103.152.113.0/24 Valid RIR databaseAPNIC 669 99% 68
103.175.98.0/23 Valid RIR databaseAPNIC 669 99% 68
103.175.99.0/24 Valid RIR databaseAPNIC 669 99% 68
134.195.101.0/24 Valid RIR databaseARIN 669 99% 68
141.193.21.0/24 Valid RIR databaseARIN, RADB 669 99% 67
2602:feda::/48 Valid RIR databaseARIN, RADB 634 100% 69
2602:feda:4::/48 Valid RIR databaseARIN, RADB 634 100% 69
2400:a6a0:200::/40 Valid RIR databaseAPNIC 633 100% 69
2602:feda:3::/48 Valid RIR databaseARIN, RADB 633 100% 69
2001:470:139::/48 Valid RIR databaseALTDB, ARIN 606 95% 68

AS-SET

PeeringDB's irr_as_set for AS46997: AS-NATOLAB. 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 (AS46997 isn't in the set, or no route object for AS46997 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 objectsAS46997 in itNot covered
AS-NATOLAB ALTDBlists itself further down1 member set in no database: AS-ROUTE48 6883797,049 Yes 5
ARIN (also)1 member set in no database: AS-APERNET 13832,423 Yes 5

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

  • ROA: origin1
  • ROA: maxLength2
  • ROA: none17
  • Route object: none15
  • Route object: RIR5
  • AS-SET: missing member1
  • Route object: not announced18
ChangePrefix or setDetailFull-table peers
ROA: origin2001:df0:ac40::/48ROAs covering it name AS140043, not AS46997. If AS46997 should announce it, add a ROA for AS46997.16 of 636
Route object: none2001:df0:ac40::/48Route objects for it name AS140043. Add a route object with origin AS46997 in the RIR database for the space.16 of 636
ROA: maxLength2602:feda:31::/48ROA 2602:feda:30::/44 AS46997 has maxLength 44; the route is a /48. Raise the maxLength, or add a ROA for 2602:feda:31::/48.16 of 636
Route object: none2602:feda:31::/48No route object for it. A route object for 2602:feda::/36 with origin AS46997 covers it (filters allowing more-specifics accept it). Add a route object with origin AS46997 in the RIR database for the space.16 of 636
ROA: maxLength2602:feda:32::/48ROA 2602:feda:30::/44 AS46997 has maxLength 44; the route is a /48. Raise the maxLength, or add a ROA for 2602:feda:32::/48.16 of 636
Route object: none2602:feda:32::/48No route object for it. A route object for 2602:feda::/36 with origin AS46997 covers it (filters allowing more-specifics accept it). Add a route object with origin AS46997 in the RIR database for the space.16 of 636
ROA: none2406:4440:40::/44No ROA covers it. Add a ROA for AS46997, maxLength 44.633 of 636
Route object: none2406:4440:40::/44Route objects for it name AS38008. Add a route object with origin AS46997 in the RIR database for the space.633 of 636
ROA: none2406:4440:d6ff::/48No ROA covers it. Add a ROA for AS46997, maxLength 48.633 of 636
Route object: none2406:4440:d6ff::/48Route objects for it name AS38008. Add a route object with origin AS46997 in the RIR database for the space.633 of 636
ROA: none2602:feda:60::/44No ROA covers it. Add a ROA for AS46997, maxLength 44.633 of 636
Route object: none2602:feda:60::/44No route object for it. A route object for 2602:feda::/36 with origin AS46997 covers it (filters allowing more-specifics accept it). Add a route object with origin AS46997 in the RIR database for the space.633 of 636
ROA: none2602:feda:f380::/44No ROA covers it. Add a ROA for AS46997, maxLength 44.633 of 636
Route object: none2602:feda:f380::/44No route object for it. A route object for 2602:feda:f300::/40 with origin AS46997 covers it (filters allowing more-specifics accept it). Add a route object with origin AS46997 in the RIR database for the space.633 of 636
ROA: none2602:feda:f390::/44No ROA covers it. Add a ROA for AS46997, maxLength 44.633 of 636
Route object: none2602:feda:f390::/44No route object for it. A route object for 2602:feda:f300::/40 with origin AS46997 covers it (filters allowing more-specifics accept it). Add a route object with origin AS46997 in the RIR database for the space.633 of 636
ROA: none2406:4440:f00::/40No ROA covers it. Add a ROA for AS46997, maxLength 40.27 of 636
Route object: none2406:4440:f00::/40No route object for it. Add a route object with origin AS46997 in the RIR database for the space.27 of 636
ROA: none2602:feda:f105::/48No ROA covers it. Add a ROA for AS46997, maxLength 48.27 of 636
Route object: none2602:feda:f105::/48No route object for it. A route object for 2602:feda:f100::/40 with origin AS46997 covers it (filters allowing more-specifics accept it). Add a route object with origin AS46997 in the RIR database for the space.27 of 636
ROA: none2407:9240:2400::/40No ROA covers it. Add a ROA for AS46997, maxLength 40.22 of 636
Route object: none2407:9240:2400::/40No route object for it. Add a route object with origin AS46997 in the RIR database for the space.22 of 636
ROA: none44.68.205.0/24No ROA covers it. Add a ROA for AS46997, maxLength 24.669 of 673
Route object: RIR44.68.205.0/24Route object only in ALTDB. Add it in the RIR database for the space.669 of 673
ROA: none2602:feda:dd0::/44No ROA covers it. Add a ROA for AS46997, maxLength 44.633 of 636
Route object: RIR2602:feda:dd0::/44Route object only in ALTDB. Add it in the RIR database for the space.633 of 636
ROA: none2406:4440:20::/44No ROA covers it. Add a ROA for AS46997, maxLength 44.633 of 636
ROA: none2602:fd92:c20::/44No ROA covers it. Add a ROA for AS46997, maxLength 44.633 of 636
ROA: none2602:fd92:c20::/45No ROA covers it. Add a ROA for AS46997, maxLength 45.633 of 636
ROA: none2602:fd92:c28::/45No ROA covers it. Add a ROA for AS46997, maxLength 45.633 of 636
ROA: none2602:feda:f100::/40No ROA covers it. Add a ROA for AS46997, maxLength 40.633 of 636
ROA: none2602:feda:f200::/44No ROA covers it. Add a ROA for AS46997, maxLength 44.633 of 636
ROA: none2602:feda:f300::/40No ROA covers it. Add a ROA for AS46997, maxLength 40.633 of 636
Route object: none2602:feda:a3::/48No route object for it. A route object for 2602:feda:a0::/44 with origin AS46997 covers it (filters allowing more-specifics accept it). Add a route object with origin AS46997 in the RIR database for the space.635 of 636
Route object: none2602:feda:8::/48No route object for it. A route object for 2602:feda::/36 with origin AS46997 covers it (filters allowing more-specifics accept it). Add a route object with origin AS46997 in the RIR database for the space.634 of 636
Route object: none2602:feda:30::/44No route object for it. A route object for 2602:feda::/36 with origin AS46997 covers it (filters allowing more-specifics accept it). Add a route object with origin AS46997 in the RIR database for the space.633 of 636
Route object: none2602:feda:38::/45No route object for it. A route object for 2602:feda::/36 with origin AS46997 covers it (filters allowing more-specifics accept it). Add a route object with origin AS46997 in the RIR database for the space.633 of 636
Route object: RIR23.247.136.0/23Route object only in ALTDB. Add it in the RIR database for the space.669 of 673
Route object: RIR23.247.136.0/24Route object only in ALTDB. Add it in the RIR database for the space.669 of 673
Route object: RIR23.247.137.0/24Route object only in ALTDB. Add it in the RIR database for the space.669 of 673
AS-SET: missing memberAS-NATOLABAS-NATOLAB (ALTDB) lists AS-ROUTE48; no IRR database read has it.

Route objects not announced

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

23.247.136.0/22ALTDB, ARINValid
23.247.138.0/23ALTDBValid
23.247.138.0/24ALTDBValid
23.247.139.0/24ALTDBValid
98.191.140.0/24ARINInvalid: origin
103.152.34.0/23ALTDBValid
134.195.100.0/23ARIN, RADBValid
2406:4440:80::/44APNICValid
2406:4440:90::/44APNICValid
2406:4440:f010::/44ALTDBNo ROA
2602:feda::/36ARINNo ROA
2602:feda:1::/48ARINInvalid: origin
2602:feda:2::/48ARINNo ROA
2602:feda:5::/48ARINValid
2602:feda:6::/48ARINNo ROA
2602:feda:a0::/44RADBNo ROA
2602:feda:ae5::/48ARINValid
2602:feda:f040::/44RADBNo 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.