bgpreport

Network · data from 2026-11-12

AS273045 AS273045 - DATAHOME S.A.

Registry name: AS273045 - DATAHOME S.A., PA · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS273045, 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.
2.57.171.0/24 Invalid: origin Other origin only 3 0%low visibility 2
179.60.144.0/24 No ROA None 672 100% 67
45.182.189.0/24 Valid RIR databaseLACNIC 673 100% 66
45.180.21.0/24 Valid RIR databaseLACNIC 672 100% 67
179.60.148.0/24 Valid RIR databaseLACNIC, RADB 672 100% 66
179.60.151.0/24 Valid RIR databaseLACNIC 672 100% 66
200.107.207.0/24 Valid RIR databaseLACNIC 672 100% 66
45.180.20.0/24 Valid RIR databaseLACNIC 671 100% 67

AS-SET

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

  • ROA: origin1
  • ROA: none1
  • Route object: none2
ChangePrefix or setDetailFull-table peers
ROA: origin2.57.171.0/24ROAs covering it name AS262287, not AS273045. If AS273045 should announce it, add a ROA for AS273045.3 of 673
Route object: none2.57.171.0/24Route objects for it name AS262287. Add a route object with origin AS273045 in the RIR database for the space.3 of 673
ROA: none179.60.144.0/24No ROA covers it. Add a ROA for AS273045, maxLength 24.672 of 673
Route object: none179.60.144.0/24No route object for it. Add a route object with origin AS273045 in the RIR database for the space.672 of 673

Route objects not announced

Every route object with origin AS273045 is announced.

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.