bgpreport

Network · data from 2026-11-12

AS216006 BLAZEHOST

Registry name: BLAZEHOST Vojtech Smrz, CZ · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS216006, 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.
82.153.113.0/24 Invalid: origin Other origin only 1 0%low visibility 1
31.56.46.0/24 Invalid: origin Other origin only 0 0%low visibility 1
2a0f:6284:500::/44 No ROA None 7 1%low visibility 6
2a06:9801:c0::/48 Valid None 634 100% 67
185.229.223.0/24 Valid RIR databaseRIPE 673 100% 67
13.143.236.0/24 Valid RIR databaseRIPE 2 0%low visibility 2

AS-SET

PeeringDB's irr_as_set for AS216006: AS216006:AS-BLAZEHOST. 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 (AS216006 isn't in the set, or no route object for AS216006 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 objectsAS216006 in itNot covered
AS216006:AS-BLAZEHOST RIPE 214 Yes 4

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

  • ROA: origin2
  • ROA: none1
  • Route object: none4
ChangePrefix or setDetailFull-table peers
ROA: origin82.153.113.0/24ROAs covering it name AS834, AS8851, AS19905, AS206509, not AS216006. If AS216006 should announce it, add a ROA for AS216006.1 of 673
Route object: none82.153.113.0/24Route objects for it name AS834. Add a route object with origin AS216006 in the RIR database for the space.1 of 673
ROA: origin31.56.46.0/24ROAs covering it name AS834, AS205544, not AS216006. If AS216006 should announce it, add a ROA for AS216006.0 of 673
Route object: none31.56.46.0/24Route objects for it name AS205544. Add a route object with origin AS216006 in the RIR database for the space.0 of 673
ROA: none2a0f:6284:500::/44No ROA covers it. Add a ROA for AS216006, maxLength 44.7 of 636
Route object: none2a0f:6284:500::/44No route object for it. Add a route object with origin AS216006 in the RIR database for the space.7 of 636
Route object: none2a06:9801:c0::/48No route object for it. Add a route object with origin AS216006 in the RIR database for the space.634 of 636

Route objects not announced

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