bgpreport

Network · data from 2026-11-12

AS28762 DataHouse SPB AS28762

Registry name: Datahouse-SPB Citytelecom LLC, RU · PeeringDB

7IPv4 routes 42.9% 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
5No ROA 0 with no route object for this origin
0Low visibility seen by under 10% of full-table peers
0Route objects not announced registered with origin AS28762, seen from no peer

Announced routes

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

31.28.3.0/24 No ROA RIR databaseRIPE 673 100% 66
185.233.93.0/24 No ROA RIR databaseRIPE 673 100% 66
188.92.182.0/24 No ROA RIR databaseRIPE 673 100% 66
193.46.65.0/24 No ROA RIR databaseRIPE 673 100% 66
2a00:12c8::/32 No ROA RIR databaseRIPE 635 100% 69
48.103.180.0/24 Valid RIR databaseRIPE 673 100% 66
89.125.55.0/24 Valid RIR databaseRIPE 673 100% 66
94.159.86.0/24 Valid RIR databaseRIPE 673 100% 66

AS-SET

PeeringDB's irr_as_set for AS28762: AS-DATAHOUSE-SPB. 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 (AS28762 isn't in the set, or no route object for AS28762 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 objectsAS28762 in itNot covered
AS-DATAHOUSE-SPB RIPE 319 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 5 are in fix.csv.

  • ROA: none5
ChangePrefix or setDetailFull-table peers
ROA: none31.28.3.0/24No ROA covers it. Add a ROA for AS28762, maxLength 24.673 of 673
ROA: none185.233.93.0/24No ROA covers it. Add a ROA for AS28762, maxLength 24.673 of 673
ROA: none188.92.182.0/24No ROA covers it. Add a ROA for AS28762, maxLength 24.673 of 673
ROA: none193.46.65.0/24No ROA covers it. Add a ROA for AS28762, maxLength 24.673 of 673
ROA: none2a00:12c8::/32No ROA covers it. Add a ROA for AS28762, maxLength 32.635 of 636

Route objects not announced

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