bgpreport

Network · data from 2026-11-12

AS273192 ALFIBER TELECOMUNICACIONES S.A.C.

Registry name: AS273192 - ALFIBER TELECOMUNICACIONES S.A.C., PE · PeeringDB

4IPv4 routes 100.0% RPKI valid · 50.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 2 with no route object for this origin
0Low visibility seen by under 10% of full-table peers
11Route objects not announced registered with origin AS273192, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS273192, 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:650::/32 No ROA Other IRR onlyRADB 636 100% 67
38.226.120.0/24 Valid Nonecovered by 38.226.120.0/23 671 100% 67
38.226.121.0/24 Valid Nonecovered by 38.226.120.0/23 670 100% 67
38.226.120.0/23 Valid RIR databaseARIN 672 100% 67
38.226.210.0/24 Valid RIR databaseARIN, RADB 672 100% 67
2803:650:100::/40 Valid RIR databaseLACNIC 636 100% 67
2803:650:900::/40 Valid RIR databaseLACNIC 634 100% 67
2803:650:d00::/40 Valid RIR databaseLACNIC 634 100% 67

AS-SET

AS273192's PeeringDB record names no AS-SET.

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

  • ROA: none1
  • Route object: none2
  • Route object: RIR1
  • Route object: not announced11
ChangePrefix or setDetailFull-table peers
ROA: none2803:650::/32No ROA covers it. Add a ROA for AS273192, maxLength 32.636 of 636
Route object: RIR2803:650::/32Route object only in RADB. Add it in the RIR database for the space.636 of 636
Route object: none38.226.120.0/24No route object for it. A route object for 38.226.120.0/23 with origin AS273192 covers it (filters allowing more-specifics accept it). Add a route object with origin AS273192 in the RIR database for the space.671 of 673
Route object: none38.226.121.0/24No route object for it. A route object for 38.226.120.0/23 with origin AS273192 covers it (filters allowing more-specifics accept it). Add a route object with origin AS273192 in the RIR database for the space.670 of 673

Route objects not announced

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

2803:650:200::/40LACNICValid
2803:650:300::/40LACNICValid
2803:650:400::/40LACNICValid
2803:650:500::/40LACNICValid
2803:650:600::/40LACNICValid
2803:650:700::/40LACNICValid
2803:650:800::/40LACNICValid
2803:650:a00::/40LACNICValid
2803:650:b00::/40LACNICValid
2803:650:c00::/40LACNICValid
2803:650:e00::/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.