bgpreport

Network · data from 2026-11-12

AS56504 HostCircle AS56504

Registry name: HOSTCIRCLE-L-NL HostCircle B.V., NL · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS56504, 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.

110.44.4.0/24 No ROA RIR databaseAPNIC, RADB 673 100% 67
154.21.215.0/24 Valid RIR databaseARIN, RADB 673 100% 67
178.237.56.0/24 Valid RIR databaseALTDB, RIPE 673 100% 67
178.237.57.0/24 Valid RIR databaseRADB, RIPE 673 100% 67
178.237.58.0/24 Valid RIR databaseRADB, RIPE 673 100% 67
178.237.59.0/24 Valid RIR databaseRIPE 673 100% 67
185.61.136.0/24 Valid RIR databaseRADB, RIPE 2 0%low visibility 2
193.91.11.0/24 Valid RIR databaseRIPE 2 0%low visibility 2
2a0d:5540:1::/48 Valid RIR databaseRADB, RIPE 1 0%low visibility 1

AS-SET

PeeringDB's irr_as_set for AS56504: AS56504:AS-ALL. 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 (AS56504 isn't in the set, or no route object for AS56504 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 objectsAS56504 in itNot covered
AS56504:AS-ALL RADB 73123 Yes 0
RIPE (also)lists itself further down 73123 Yes 0

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 6 are in fix.csv.

  • ROA: none1
  • Route object: not announced5
ChangePrefix or setDetailFull-table peers
ROA: none110.44.4.0/24No ROA covers it. Add a ROA for AS56504, maxLength 24.673 of 673

Route objects not announced

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

154.22.149.0/24ARINValid
154.28.156.0/24ARIN, RADBValid
154.51.14.0/24RADBNo ROA
185.251.229.0/24RADB, RIPEValid
2a0d:5540:2::/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.