bgpreport

Network · data from 2026-11-12

AS273883 MEGATEL-EC S.A.

Registry name: AS273883 - MEGATEL-EC S.A., EC · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS273883, 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:4350:400::/48 Invalid: maxLength Nonecovered by 2803:4350:400::/40 5 1%low visibility 4
2803:4350:1600::/40 No ROA Nonecovered by 2803:4350::/32 636 100% 67
2803:4350::/32 No ROA Other IRR onlyRADB 633 100% 67
167.250.132.0/24 Valid RIR databaseLACNIC, RADB 672 100% 66
167.250.133.0/24 Valid RIR databaseLACNIC, RADB 671 100% 67
2803:4350:100::/40 Valid RIR databaseLACNIC 636 100% 67
2803:4350:200::/40 Valid RIR databaseLACNIC 636 100% 67
2803:4350:400::/40 Valid RIR databaseLACNIC 636 100% 67
2803:4350:500::/40 Valid RIR databaseLACNIC 636 100% 67
2803:4350:600::/40 Valid RIR databaseLACNIC 636 100% 67
2803:4350:700::/40 Valid RIR databaseLACNIC 636 100% 67
2803:4350:b00::/40 Valid RIR databaseLACNIC 636 100% 67
2803:4350:c00::/40 Valid RIR databaseLACNIC 636 100% 67

AS-SET

AS273883'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 13 are in fix.csv.

  • ROA: maxLength1
  • ROA: none2
  • Route object: none2
  • Route object: RIR1
  • Route object: not announced7
ChangePrefix or setDetailFull-table peers
ROA: maxLength2803:4350:400::/48ROA 2803:4350:400::/40 AS273883 has maxLength 40; the route is a /48. Raise the maxLength, or add a ROA for 2803:4350:400::/48.5 of 636
Route object: none2803:4350:400::/48No route object for it. A route object for 2803:4350:400::/40 with origin AS273883 covers it (filters allowing more-specifics accept it). Add a route object with origin AS273883 in the RIR database for the space.5 of 636
ROA: none2803:4350:1600::/40No ROA covers it. Add a ROA for AS273883, maxLength 40.636 of 636
Route object: none2803:4350:1600::/40No route object for it. A route object for 2803:4350::/32 with origin AS273883 covers it (filters allowing more-specifics accept it). Add a route object with origin AS273883 in the RIR database for the space.636 of 636
ROA: none2803:4350::/32No ROA covers it. Add a ROA for AS273883, maxLength 32.633 of 636
Route object: RIR2803:4350::/32Route object only in RADB. Add it in the RIR database for the space.633 of 636

Route objects not announced

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

167.250.132.0/23LACNICValid
2803:4350:300::/40LACNICValid
2803:4350:800::/40LACNICValid
2803:4350:a00::/40LACNICValid
2803:4350:d00::/40LACNICValid
2803:4350:e00::/40LACNICValid
2803:4350:f00::/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.