bgpreport

Network · data from 2026-11-12

AS214467 digided-as DIGIDED LTD

Registry name: digided-as DIGIDED LTD, GB · not in PeeringDB

10IPv4 routes 90.0% RPKI valid · 90.0% with a route object
0IPv6 routes
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
2Route objects not announced registered with origin AS214467, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS214467, 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.
147.90.17.0/24 No ROA Other origin only 2 0%low visibility 1
87.83.84.0/24 Valid RIR databaseRADB, RIPE 673 100% 66
144.225.12.0/24 Valid RIR databaseARIN, RADB 673 100% 67
164.37.230.0/24 Valid RIR databaseRADB, RIPE 673 100% 67
172.110.208.0/24 Valid RIR databaseRIPE 673 100% 66
185.142.31.0/24 Valid RIR databaseRIPE 673 100% 67
154.222.10.0/24 Valid RIR databaseAFRINIC, RADB 672 100% 66
193.22.162.0/24 Valid RIR databaseRIPE 672 100% 67
202.71.8.0/24 Valid RIR databaseRIPE 672 100% 67
185.142.30.0/24 Valid RIR databaseRIPE 671 100% 68

AS-SET

AS214467 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: none1
  • Route object: none1
  • Route object: not announced2
ChangePrefix or setDetailFull-table peers
ROA: none147.90.17.0/24No ROA covers it. Add a ROA for AS214467, maxLength 24.2 of 673
Route object: none147.90.17.0/24Route objects for it name AS834, AS207158. Add a route object with origin AS214467 in the RIR database for the space.2 of 673

Route objects not announced

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

87.86.95.0/24RADB, RIPEValid
103.175.128.0/24APNICValid

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.