bgpreport

Network · data from 2026-11-12

AS272139 AS272139 - @ DIGITAL GROUP S.A.S.

Registry name: AS272139 - @ DIGITAL GROUP S.A.S., CO · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS272139, 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.

181.225.190.0/24 Valid Other origin only 673 100% 67
181.225.189.0/24 Valid None 672 100% 67
2803:53e0:3100::/40 Valid Nonecovered by 2803:53e0::/32 636 100% 67
2803:53e0:a000::/48 Valid Nonecovered by 2803:53e0::/32 636 100% 67
2803:53e0:2000::/36 Valid Nonecovered by 2803:53e0::/32 635 100% 68
2803:53e0:1003::/48 Valid Other origin onlycovered by 2803:53e0::/32 201 32% 59

AS-SET

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

  • Route object: none6
  • Route object: not announced1
ChangePrefix or setDetailFull-table peers
Route object: none181.225.190.0/24Route objects for it name AS52468. Add a route object with origin AS272139 in the RIR database for the space.673 of 673
Route object: none181.225.189.0/24No route object for it. Add a route object with origin AS272139 in the RIR database for the space.672 of 673
Route object: none2803:53e0:3100::/40No route object for it. A route object for 2803:53e0::/32 with origin AS272139 covers it (filters allowing more-specifics accept it). Add a route object with origin AS272139 in the RIR database for the space.636 of 636
Route object: none2803:53e0:a000::/48No route object for it. A route object for 2803:53e0::/32 with origin AS272139 covers it (filters allowing more-specifics accept it). Add a route object with origin AS272139 in the RIR database for the space.636 of 636
Route object: none2803:53e0:2000::/36No route object for it. A route object for 2803:53e0::/32 with origin AS272139 covers it (filters allowing more-specifics accept it). Add a route object with origin AS272139 in the RIR database for the space.635 of 636
Route object: none2803:53e0:1003::/48Route objects for it name AS52468. A route object for 2803:53e0::/32 with origin AS272139 covers it (filters allowing more-specifics accept it). Add a route object with origin AS272139 in the RIR database for the space.201 of 636

Route objects not announced

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

2803:53e0::/32RADBValid

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.