bgpreport

Network · data from 2026-11-12

AS273828 AS273828 - DAMOA SA

Registry name: AS273828 - DAMOA SA, PY · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS273828, 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.92.134.0/24 Valid RIR databaseARIN 670 100% 66
154.3.61.0/24 Valid RIR databaseARIN 668 99% 67
2803:b150::/32 Valid RIR databaseALTDB, LACNIC 633 100% 67
2803:b150::/36 Valid RIR databaseALTDB, LACNIC 633 100% 67
2803:b150:8000::/33 Valid RIR databaseLACNIC 633 100% 67
2803:b150:8000::/36 Valid RIR databaseLACNIC 633 100% 67

AS-SET

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

  • Route object: not announced1

Route objects not announced

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

2803:b150::/33LACNICValid

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.