bgpreport

Network · data from 2026-11-12

AS211301 Unesty

Registry name: UNESTY Collin Schneeweiss trading as Unesty Company, DE · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS211301, 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.
2a0f:5707:aa61::/48 Valid None 636 100% 67
179.61.221.0/24 Valid RIR databaseRIPE 673 100% 67
5.175.249.0/24 Valid RIR databaseRIPE 671 100% 67
89.144.30.0/24 Valid RIR databaseRIPE 671 100% 67
179.61.138.0/24 Valid RIR databaseRADB, RIPE 671 100% 67
179.61.251.0/24 Valid RIR databaseRADB, RIPE 671 100% 67
181.214.99.0/24 Valid RIR databaseRADB, RIPE 671 100% 67
181.214.231.0/24 Valid RIR databaseRADB, RIPE 671 100% 67
77.90.57.0/24 Valid RIR databaseRIPE 670 100% 67
2a0f:5707:aa62::/48 Valid RIR databaseRIPE 636 100% 67
2a0f:5707:aa63::/48 Valid RIR databaseRIPE 636 100% 67
2a0f:5707:aa64::/48 Valid RIR databaseRIPE 636 100% 67
2a0f:5707:aa65::/48 Valid RIR databaseRIPE 636 100% 67
2a0f:5707:aa66::/48 Valid RIR databaseRIPE 636 100% 67
2a0f:5707:aa67::/48 Valid RIR databaseRIPE 636 100% 67
2a0f:5707:aa68::/48 Valid RIR databaseRIPE 636 100% 67
2a0f:5707:aa69::/48 Valid RIR databaseRIPE 636 100% 67
2a0f:5707:aa6a::/48 Valid RIR databaseRIPE 636 100% 67
2a0f:5707:aa6b::/48 Valid RIR databaseRIPE 636 100% 67
2a0f:5707:aaf1::/48 Valid RIR databaseRIPE 636 100% 67
2a0f:5707:aaf3::/48 Valid RIR databaseRIPE 636 100% 67
2a0f:5707:aa6f::/48 Valid RIR databaseRIPE 635 100% 69
2a0f:5707:aaf2::/48 Valid RIR databaseRIPE 1 0%low visibility 1

AS-SET

AS211301'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.

  • Route object: none1
  • Route object: not announced3
ChangePrefix or setDetailFull-table peers
Route object: none2a0f:5707:aa61::/48No route object for it. Add a route object with origin AS211301 in the RIR database for the space.636 of 636

Route objects not announced

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

2a0f:5707:aa60::/48RADBValid
2a0f:5707:aaf0::/44RADB, RIPEValid
2a0f:5707:aaf0::/48RIPEValid

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.