bgpreport

Network · data from 2026-11-12

AS33962 DataHouse EKT AS33962

Registry name: DataHouse-EKT Citytelecom LLC, RU · PeeringDB

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

Announced routes

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

164.215.72.0/24 No ROA RIR databaseRIPE 672 100% 66
164.215.73.0/24 No ROA RIR databaseRIPE 672 100% 66
164.215.75.0/24 No ROA RIR databaseRIPE 669 99% 67
2a0c:e100::/29 No ROA RIR databaseRIPE 635 100% 69

AS-SET

PeeringDB's irr_as_set for AS33962: AS-DATAHOUSE. 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 (AS33962 isn't in the set, or no route object for AS33962 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 objectsAS33962 in itNot covered
AS-DATAHOUSE RIPE 12694,675 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 7 are in fix.csv.

  • ROA: none4
  • Route object: not announced3
ChangePrefix or setDetailFull-table peers
ROA: none164.215.72.0/24No ROA covers it. Add a ROA for AS33962, maxLength 24.672 of 673
ROA: none164.215.73.0/24No ROA covers it. Add a ROA for AS33962, maxLength 24.672 of 673
ROA: none164.215.75.0/24No ROA covers it. Add a ROA for AS33962, maxLength 24.669 of 673
ROA: none2a0c:e100::/29No ROA covers it. Add a ROA for AS33962, maxLength 29.635 of 636

Route objects not announced

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

82.196.83.0/24RIPEInvalid: origin
84.204.128.0/22RIPEInvalid: origin
84.204.128.0/24RIPEInvalid: 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.