bgpreport

Network · data from 2026-11-12

AS214663 DanBot-Hosting-LTD DanBot Hosting LTD

Registry name: DanBot-Hosting-LTD DanBot Hosting LTD, GB · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS214663, 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.
2a06:9801:f80::/44 No ROA None 635 100% 67
2a0f:85c1:cd2::/48 No ROA RIR databaseRIPE 635 100% 69
5.199.2.0/24 Valid RIR databaseRADB, RIPE 673 100% 67
185.223.80.0/24 Valid RIR databaseRADB, RIPE 673 100% 67
82.38.134.0/24 Valid RIR databaseRADB, RIPE 671 100% 67

AS-SET

AS214663 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: none2
  • Route object: none1
  • Route object: not announced1
ChangePrefix or setDetailFull-table peers
ROA: none2a06:9801:f80::/44No ROA covers it. Add a ROA for AS214663, maxLength 44.635 of 636
Route object: none2a06:9801:f80::/44No route object for it. Add a route object with origin AS214663 in the RIR database for the space.635 of 636
ROA: none2a0f:85c1:cd2::/48No ROA covers it. Add a ROA for AS214663, maxLength 48.635 of 636

Route objects not announced

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

2a07:54c1:55ff::/48RIPEInvalid: origin

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.