bgpreport

Network · data from 2026-11-12

AS35032 NIS

Registry name: TAHIONISP-AS LLC SIP "NIS", RU · PeeringDB

18IPv4 routes 100.0% RPKI valid · 100.0% with a route object
12IPv6 routes 100.0% RPKI valid · 100.0% with a route object
0RPKI invalid 0 origin · 0 maxLength
0No 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 AS35032, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS35032, 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.
80.76.128.0/22 Valid RIR databaseRIPE 673 100% 66
80.76.132.0/23 Valid RIR databaseRIPE 673 100% 66
80.76.134.0/23 Valid RIR databaseRIPE 673 100% 66
80.76.136.0/23 Valid RIR databaseRIPE 673 100% 66
80.76.138.0/23 Valid RIR databaseRIPE 673 100% 66
80.76.140.0/22 Valid RIR databaseRIPE 673 100% 66
85.236.160.0/20 Valid RIR databaseRIPE 673 100% 66
85.236.176.0/20 Valid RIR databaseRIPE 673 100% 66
109.124.192.0/19 Valid RIR databaseRIPE 673 100% 66
109.124.224.0/21 Valid RIR databaseRIPE 673 100% 66
109.124.232.0/21 Valid RIR databaseRIPE 673 100% 66
109.124.240.0/21 Valid RIR databaseRIPE 673 100% 66
109.124.248.0/22 Valid RIR databaseRIPE 673 100% 66
109.124.252.0/23 Valid RIR databaseRIPE 673 100% 66
109.124.254.0/23 Valid RIR databaseRIPE 673 100% 66
185.224.8.0/22 Valid RIR databaseRIPE 673 100% 66
193.27.236.0/22 Valid RIR databaseRIPE 673 100% 66
193.27.240.0/23 Valid RIR databaseRIPE 673 100% 66
2a13:73c0::/34 Valid RIR databaseRIPE 636 100% 69
2a13:73c0:4000::/34 Valid RIR databaseRIPE 636 100% 69
2a13:73c0:8000::/34 Valid RIR databaseRIPE 636 100% 69
2a13:73c0:c000::/34 Valid RIR databaseRIPE 636 100% 69
2a13:73c1::/34 Valid RIR databaseRIPE 636 100% 69
2a13:73c1:4000::/34 Valid RIR databaseRIPE 636 100% 69
2a13:73c1:8000::/34 Valid RIR databaseRIPE 636 100% 69
2a13:73c1:c000::/34 Valid RIR databaseRIPE 636 100% 69
2a13:73c6::/32 Valid RIR databaseRIPE 636 100% 69
2a13:73c7::/32 Valid RIR databaseRIPE 636 100% 69
2a13:73c2::/31 Valid RIR databaseRIPE 635 100% 69
2a13:73c4::/31 Valid RIR databaseRIPE 635 100% 69

AS-SET

PeeringDB's irr_as_set for AS35032: AS-TAHION. 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 (AS35032 isn't in the set, or no route object for AS35032 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 objectsAS35032 in itNot covered
AS-TAHION RIPE 5135 Yes 0

Fix list

Nothing to change: every route is RPKI valid with a route object in an RIR database, and every route object is announced.

Route objects not announced

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