bgpreport

Network · data from 2026-11-12

AS209505 Unchained ISP AS209505

Registry name: UNCHAINEDISP Unchained ISP Limited, GB · PeeringDB

5IPv4 routes 80.0% RPKI valid · 80.0% with a route object
4IPv6 routes 75.0% RPKI valid · 75.0% with a route object
2RPKI invalid 1 origin · 1 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 AS209505, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS209505, 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.
212.60.144.0/24 Invalid: origin Other origin only 2 0%low visibility 2
2a0b:9400:8::/48 Invalid: maxLength Nonecovered by 2a0b:9400::/30 1 0%low visibility 1
78.41.136.0/24 Valid RIR databaseRIPE 673 100% 67
89.33.9.0/24 Valid RIR databaseRIPE 673 100% 67
185.250.8.0/22 Valid RIR databaseRIPE 673 100% 67
195.10.233.0/24 Valid RIR databaseRIPE 673 100% 67
2a0b:9404::/32 Valid RIR databaseRIPE 636 100% 67
2a0b:9400::/30 Valid RIR databaseRIPE 635 100% 67
2a13:3840:4000::/34 Valid RIR databaseRIPE 635 100% 67

AS-SET

PeeringDB's irr_as_set for AS209505: AS-UNCHAINED. Expanded from the day's IRR dumps the way bgpq4 does against whois.radb.net: a name with a database is read from that database only, one without from the first database in RADB's order. "Not covered" = this network's own routes that a filter built from the set would leave out (AS209505 isn't in the set, or no route object for AS209505 covers the route; more-specifics of a route object are accepted down to /24 and /48, as with bgpq4 -A -R 24 / -R 48). Customers' routes aren't counted: the collectors show each route's origin, not which network it came through.

NameDatabaseASNsSets Route objectsAS209505 in itNot covered
AS-UNCHAINED RIPE 5160 Yes 1

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: maxLength1
  • Route object: none2
ChangePrefix or setDetailFull-table peers
ROA: origin212.60.144.0/24ROAs covering it name AS199550, not AS209505. If AS209505 should announce it, add a ROA for AS209505.2 of 673
Route object: none212.60.144.0/24Route objects for it name AS199550. Add a route object with origin AS209505 in the RIR database for the space.2 of 673
ROA: maxLength2a0b:9400:8::/48ROA 2a0b:9400::/30 AS209505 has maxLength 30; the route is a /48. Raise the maxLength, or add a ROA for 2a0b:9400:8::/48.1 of 636
Route object: none2a0b:9400:8::/48No route object for it. A route object for 2a0b:9400::/30 with origin AS209505 covers it (filters allowing more-specifics accept it). Add a route object with origin AS209505 in the RIR database for the space.1 of 636

Route objects not announced

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