bgpreport

Network · data from 2026-11-12

AS40880 NAICOM CORPORATION

Registry name: NAICOM - NAICOM CORPORATION, PR · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS40880, 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.252.76.0/22 No ROA Other IRR onlyRADB 667 99% 68
38.252.79.0/24 No ROA Other IRR onlyRADB 667 99% 68
67.206.255.0/24 No ROA Other IRR onlyRADB 667 99% 68
2602:fe09:f00::/40 Valid Other IRR onlyRADB 631 99% 69
2602:fe09:f00::/48 Valid Other IRR onlyRADB 631 99% 69

AS-SET

PeeringDB's irr_as_set for AS40880: AS40880:AS-NAICOM. 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 (AS40880 isn't in the set, or no route object for AS40880 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 objectsAS40880 in itNot covered
AS40880:AS-NAICOM RADB 4116 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 8 are in fix.csv.

  • ROA: none3
  • Route object: RIR5
ChangePrefix or setDetailFull-table peers
ROA: none38.252.76.0/22No ROA covers it. Add a ROA for AS40880, maxLength 22.667 of 673
Route object: RIR38.252.76.0/22Route object only in RADB. Add it in the RIR database for the space.667 of 673
ROA: none38.252.79.0/24No ROA covers it. Add a ROA for AS40880, maxLength 24.667 of 673
Route object: RIR38.252.79.0/24Route object only in RADB. Add it in the RIR database for the space.667 of 673
ROA: none67.206.255.0/24No ROA covers it. Add a ROA for AS40880, maxLength 24.667 of 673
Route object: RIR67.206.255.0/24Route object only in RADB. Add it in the RIR database for the space.667 of 673
Route object: RIR2602:fe09:f00::/40Route object only in RADB. Add it in the RIR database for the space.631 of 636
Route object: RIR2602:fe09:f00::/48Route object only in RADB. Add it in the RIR database for the space.631 of 636

Route objects not announced

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