Network · data from 2026-11-12
AS207810 VirusNet LLC
Registry name: VTelecom "Virus Net" LLC, AM · PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS207810, 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.
| 5.134.84.0/23 | Valid | RIR databaseRIPE | 673 100% |
| 45.159.74.0/23 | Valid | RIR databaseRIPE | 673 100% |
| 185.167.217.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 217.113.12.0/22 | Valid | RIR databaseRIPE | 673 100% |
| 45.159.73.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 46.70.252.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 185.21.253.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 217.113.18.0/23 | Valid | RIR databaseRIPE | 672 100% |
| 45.159.74.0/24 | Valid | RIR databaseRIPE | 2 0%low visibility |
| 45.159.75.0/24 | Valid | RIR databaseRIPE | 2 0%low visibility |
AS-SET
PeeringDB's irr_as_set for AS207810: AS207810: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 (AS207810 isn't in the set, or no route object for AS207810 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.
| Name | Database | ASNs | Sets | AS207810 in it | Not covered | |
|---|---|---|---|---|---|---|
| AS207810:AS-ALL | In no IRR database read today. | |||||
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.
- AS-SET: not found1
| Change | Prefix or set | Detail |
|---|---|---|
| AS-SET: not found | AS207810:AS-ALL | PeeringDB names AS207810:AS-ALL; no IRR database read has it. |
Route objects not announced
Every route object with origin AS207810 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.