bgpreport

Network · data from 2026-11-12

AS210269 HostCircle AS210269

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

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS210269, 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.
2a0d:5540::/48 Invalid: origin RIR databaseRIPE 1 0%low visibility 1
2a12:bec0:100::/44 Valid RIR databaseRADB, RIPE 1 0%low visibility 1

AS-SET

PeeringDB's irr_as_set for AS210269: AS210269: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 (AS210269 isn't in the set, or no route object for AS210269 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 objectsAS210269 in itNot covered
AS210269:AS-ALL RADB 3121 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 1 are in fix.csv.

  • ROA: origin1
ChangePrefix or setDetailFull-table peers
ROA: origin2a0d:5540::/48ROAs covering it name AS56504, not AS210269. If AS210269 should announce it, add a ROA for AS210269.1 of 636

Route objects not announced

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