bgpreport

Network · data from 2026-11-12

AS272964 AS272964 - TAMAYO MAGDA JUDITH

Registry name: AS272964 - TAMAYO MAGDA JUDITH, AR · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS272964, 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.
38.156.71.0/24 No ROA Other origin only 38 6%low visibility 26
138.117.13.0/24 Valid RIR databaseLACNIC 670 100% 67
2803:590::/32 Valid RIR databaseLACNIC 636 100% 67

AS-SET

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

  • ROA: none1
  • Route object: none1
  • Route object: not announced1
ChangePrefix or setDetailFull-table peers
ROA: none38.156.71.0/24No ROA covers it. Add a ROA for AS272964, maxLength 24.38 of 673
Route object: none38.156.71.0/24Route objects for it name AS272739. Add a route object with origin AS272964 in the RIR database for the space.38 of 673

Route objects not announced

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

181.209.124.172/30LACNICValid

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.