bgpreport

Network · data from 2026-11-12

AS26370 PALCOM

Registry name: AS-PALCOM - Pal Communications LLC, US · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS26370, 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.
2602:fe68:fe0::/44 Valid Nonecovered by 2602:fe68::/36 634 100% 69
130.51.192.0/24 Valid Nonecovered by 130.51.192.0/23 99 15% 37
130.51.193.0/24 Valid Nonecovered by 130.51.192.0/23 99 15% 37
23.178.224.0/24 Valid RIR databaseARIN 672 100% 68
198.163.75.0/24 Valid RIR databaseARIN 672 100% 68
130.51.192.0/23 Valid RIR databaseARIN 670 100% 68
2602:fe68::/36 Valid RIR databaseARIN 635 100% 69

AS-SET

PeeringDB's irr_as_set for AS26370: AS-PALCNET. 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 (AS26370 isn't in the set, or no route object for AS26370 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 objectsAS26370 in itNot covered
AS-PALCNET ARINlists itself further down 8592 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 3 are in fix.csv.

  • Route object: none3
ChangePrefix or setDetailFull-table peers
Route object: none2602:fe68:fe0::/44No route object for it. A route object for 2602:fe68::/36 with origin AS26370 covers it (filters allowing more-specifics accept it). Add a route object with origin AS26370 in the RIR database for the space.634 of 636
Route object: none130.51.192.0/24No route object for it. A route object for 130.51.192.0/23 with origin AS26370 covers it (filters allowing more-specifics accept it). Add a route object with origin AS26370 in the RIR database for the space.99 of 673
Route object: none130.51.193.0/24No route object for it. A route object for 130.51.192.0/23 with origin AS26370 covers it (filters allowing more-specifics accept it). Add a route object with origin AS26370 in the RIR database for the space.99 of 673

Route objects not announced

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