bgpreport

Network · data from 2026-11-12

AS274877 PARMO NETWORK

Registry name: AS274877 - JOSE PABLO ARIAS MORA, CR · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS274877, 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.
2803:3a30:a000::/36 Valid Nonecovered by 2803:3a30::/32 1 0%low visibility 1
2803:3a30:b000::/36 Valid Nonecovered by 2803:3a30::/32 1 0%low visibility 1
45.194.122.0/24 Valid RIR databaseAFRINIC, RADB 665 99% 68
2803:3a30::/32 Valid RIR databaseLACNIC 636 100% 67

AS-SET

PeeringDB's irr_as_set for AS274877: AS274877:AS-PARMO. 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 (AS274877 isn't in the set, or no route object for AS274877 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 objectsAS274877 in itNot covered
AS274877:AS-PARMO LACNIC 215 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: none2
  • Route object: not announced1
ChangePrefix or setDetailFull-table peers
Route object: none2803:3a30:a000::/36No route object for it. A route object for 2803:3a30::/32 with origin AS274877 covers it (filters allowing more-specifics accept it). Add a route object with origin AS274877 in the RIR database for the space.1 of 636
Route object: none2803:3a30:b000::/36No route object for it. A route object for 2803:3a30::/32 with origin AS274877 covers it (filters allowing more-specifics accept it). Add a route object with origin AS274877 in the RIR database for the space.1 of 636

Route objects not announced

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

2a06:9801:fcd::/48RIPEValid

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.