bgpreport

Network · data from 2026-11-12

AS273127 AMBAFIBER

Registry name: AS273127 - VITERI HERNANDEZ CHRYSTIAN PATRICIO, EC · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS273127, 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:2450::/32 No ROA Other IRR onlyRADB 634 100% 67
38.121.225.0/24 Valid RIR databaseARIN, RADB 671 100% 67
2803:2450:600::/40 Valid RIR databaseLACNIC 636 100% 67
2803:2450:200::/40 Valid RIR databaseLACNIC, RADB 635 100% 67
2803:2450:400::/40 Valid RIR databaseLACNIC, RADB 635 100% 67

AS-SET

PeeringDB's irr_as_set for AS273127: AS273127. 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 (AS273127 isn't in the set, or no route object for AS273127 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 objectsAS273127 in itNot covered
AS273127 A single AS number, not a set: AS273127 (this network), 12 route objects.

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

  • ROA: none1
  • Route object: RIR1
  • Route object: not announced7
ChangePrefix or setDetailFull-table peers
ROA: none2803:2450::/32No ROA covers it. Add a ROA for AS273127, maxLength 32.634 of 636
Route object: RIR2803:2450::/32Route object only in RADB. Add it in the RIR database for the space.634 of 636

Route objects not announced

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

2803:2450:300::/40LACNICValid
2803:2450:500::/40LACNICValid
2803:2450:700::/40LACNICValid
2803:2450:800::/40LACNICValid
2803:2450:900::/40LACNICValid
2803:2450:a00::/40LACNICValid
2803:2450:b00::/40LACNICValid

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.