bgpreport

Network · data from 2026-11-12

AS274202 AS274202 - GRUPO MULTIMEDIA S&G, C.A

Registry name: AS274202 - GRUPO MULTIMEDIA S&G, C.A, VE · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS274202, 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.
154.40.142.0/24 Valid Nonecovered by 154.40.142.0/23 673 100% 67
154.40.143.0/24 Valid Nonecovered by 154.40.142.0/23 669 99% 67
38.127.221.0/24 Valid RIR databaseARIN 671 100% 67
38.127.220.0/24 Valid RIR databaseARIN 670 100% 67
2803:9c30::/36 Valid RIR databaseLACNIC 605 95% 67
2803:9c30:1000::/36 Valid RIR databaseLACNIC 605 95% 67
2803:9c30:2000::/36 Valid RIR databaseLACNIC 605 95% 67
2803:9c30:3000::/36 Valid RIR databaseLACNIC 605 95% 67
2803:9c30:4000::/36 Valid RIR databaseLACNIC 604 95% 67

AS-SET

AS274202 isn't in PeeringDB, where networks name their 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 16 are in fix.csv.

  • Route object: none2
  • Route object: not announced14
ChangePrefix or setDetailFull-table peers
Route object: none154.40.142.0/24No route object for it. A route object for 154.40.142.0/23 with origin AS274202 covers it (filters allowing more-specifics accept it). Add a route object with origin AS274202 in the RIR database for the space.673 of 673
Route object: none154.40.143.0/24No route object for it. A route object for 154.40.142.0/23 with origin AS274202 covers it (filters allowing more-specifics accept it). Add a route object with origin AS274202 in the RIR database for the space.669 of 673

Route objects not announced

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

38.127.220.0/23ARINValid
154.40.142.0/23ARIN, RADBValid
2803:9c30::/32LACNICValid
2803:9c30:5000::/36LACNICValid
2803:9c30:6000::/36LACNICValid
2803:9c30:7000::/36LACNICValid
2803:9c30:8000::/36LACNICValid
2803:9c30:9000::/36LACNICValid
2803:9c30:a000::/36LACNICValid
2803:9c30:b000::/36LACNICValid
2803:9c30:c000::/36LACNICValid
2803:9c30:d000::/36LACNICValid
2803:9c30:e000::/36LACNICValid
2803:9c30:f000::/36LACNICValid

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.