bgpreport

Network · data from 2026-11-12

AS210814 VUNIFY

Registry name: VUNIFY VUNIFY LTD, GB · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS210814, 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.
82.29.79.0/24 Invalid: origin Other origin only 10 1%low visibility 7
82.21.41.0/24 Invalid: origin Other origin only 1 0%low visibility 1
87.199.153.0/24 Valid RIR databaseRIPE 673 100% 66
87.199.155.0/24 Valid RIR databaseRIPE 673 100% 67
136.148.148.0/24 Valid RIR databaseRIPE 673 100% 67
199.204.26.0/24 Valid RIR databaseRIPE 673 100% 67
222.167.222.0/24 Valid RIR databaseRADB, RIPE 673 100% 66
109.122.255.0/24 Valid RIR databaseRIPE 672 100% 66
87.199.152.0/24 Valid RIR databaseRIPE 671 100% 67
94.183.172.0/24 Valid RIR databaseRIPE 671 100% 66
199.204.25.0/24 Valid RIR databaseRIPE 671 100% 66
199.204.27.0/24 Valid RIR databaseRIPE 671 100% 67
136.148.150.0/24 Valid RIR databaseRIPE 670 100% 67
136.148.151.0/24 Valid RIR databaseRIPE 670 100% 67
136.148.149.0/24 Valid RIR databaseRIPE 669 99% 67
185.222.28.0/24 Valid RIR databaseRADB, RIPE 669 99% 67
62.60.190.0/24 Valid RIR databaseRIPE 665 99% 66
185.119.205.0/24 Valid RIR databaseRIPE 645 96% 67
2a05:3a80:3::/48 Valid RIR databaseRIPE 635 100% 67
2a05:3a81:1::/48 Valid RIR databaseRIPE 635 100% 67
2a05:3a80::/48 Valid RIR databaseRIPE 634 100% 67
2a05:3a80:1::/48 Valid RIR databaseRIPE 634 100% 67
2a05:3a80:2::/48 Valid RIR databaseRIPE 633 100% 69

AS-SET

AS210814's PeeringDB record names no 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: origin2
  • Route object: none2
ChangePrefix or setDetailFull-table peers
ROA: origin82.29.79.0/24ROAs covering it name AS214716, not AS210814. If AS210814 should announce it, add a ROA for AS210814.10 of 673
Route object: none82.29.79.0/24Route objects for it name AS214716. Add a route object with origin AS210814 in the RIR database for the space.10 of 673
ROA: origin82.21.41.0/24ROAs covering it name AS201256, not AS210814. If AS210814 should announce it, add a ROA for AS210814.1 of 673
Route object: none82.21.41.0/24Route objects for it name AS201256. Add a route object with origin AS210814 in the RIR database for the space.1 of 673

Route objects not announced

Every route object with origin AS210814 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.