Network · data from 2026-11-12
AS30286 ThreatMetrix
Registry name: THM - ThreatMetrix Inc., US · PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS30286, 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.
| 91.235.135.0/24 | Valid | Nonecovered by 91.235.132.0/22 | 673 100% |
| 185.32.243.0/24 | Valid | Nonecovered by 185.32.242.0/23 | 673 100% |
| 192.225.157.0/24 | Valid | Nonecovered by 192.225.156.0/22 | 673 100% |
| 192.225.158.0/24 | Valid | Nonecovered by 192.225.156.0/22 | 673 100% |
| 192.225.159.0/24 | Valid | Nonecovered by 192.225.156.0/22 | 673 100% |
| 199.101.156.0/24 | Valid | Nonecovered by 199.101.156.0/23 | 673 100% |
| 199.101.157.0/24 | Valid | Nonecovered by 199.101.156.0/23 | 673 100% |
| 2a03:7b40:3::/48 | Valid | Nonecovered by 2a03:7b40::/32 | 636 100% |
| 91.235.132.0/22 | Valid | Other IRR onlyRADB | 673 100% |
| 145.43.252.0/23 | Valid | Other IRR onlyRADB | 673 100% |
| 185.32.240.0/23 | Valid | Other IRR onlyRADB | 673 100% |
| 185.32.242.0/23 | Valid | Other IRR onlyRADB | 673 100% |
| 192.225.156.0/24 | Valid | Other IRR onlyRADB | 673 100% |
| 69.84.176.0/24 | Valid | Other IRR onlyRADB | 671 100% |
| 2a03:7b40:2::/48 | Valid | Other IRR onlyRADB | 636 100% |
| 2a03:7b40::/48 | Valid | Other IRR onlyRADB | 635 100% |
| 2a03:7b40:1::/48 | Valid | Other IRR onlyRADB | 635 100% |
| 69.84.177.6/32 | Valid | Other IRR onlyRADB | 24 4%low visibility |
| 69.84.177.7/32 | Valid | Other IRR onlyRADB | 24 4%low visibility |
| 91.235.135.229/32 | Valid | Other IRR onlyRADB | 24 4%low visibility |
| 91.235.135.230/32 | Valid | Other IRR onlyRADB | 24 4%low visibility |
| 145.43.252.20/32 | Valid | Other IRR onlyRADB | 24 4%low visibility |
| 145.43.252.21/32 | Valid | Other IRR onlyRADB | 24 4%low visibility |
| 192.225.156.0/22 | Valid | RIR databaseARIN, RADB | 671 100% |
| 199.101.156.0/23 | Valid | RIR databaseARIN, RADB | 671 100% |
| 199.101.158.0/23 | Valid | RIR databaseARIN, RADB | 671 100% |
| 69.84.177.0/24 | Valid | RIR databaseARIN, RADB | 668 99% |
| 2620:f3::/48 | Valid | RIR databaseARIN, RADB | 636 100% |
| 192.225.156.20/32 | Valid | RIR databaseARIN, RADB | 24 4%low visibility |
| 192.225.156.21/32 | Valid | RIR databaseARIN, RADB | 24 4%low visibility |
AS-SET
PeeringDB's irr_as_set for AS30286: RS-SAC RS-AMS RS-ICE. 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 (AS30286 isn't in the set, or no route object for AS30286 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 | AS30286 in it | Not covered | |
|---|---|---|---|---|---|---|
| RS-SAC | A route-set, not an AS-SET; route-sets aren't expanded. | |||||
| RS-AMS | A route-set, not an AS-SET; route-sets aren't expanded. | |||||
| RS-ICE | A route-set, not an AS-SET; route-sets aren't expanded. | |||||
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 32 are in fix.csv.
- Route object: none8
- Route object: RIR15
- Route object: not announced9
| Change | Prefix or set | Detail |
|---|---|---|
| Route object: none | 91.235.135.0/24 | No route object for it. A route object for 91.235.132.0/22 with origin AS30286 covers it (filters allowing more-specifics accept it). Add a route object with origin AS30286 in the RIR database for the space. |
| Route object: none | 185.32.243.0/24 | No route object for it. A route object for 185.32.242.0/23 with origin AS30286 covers it (filters allowing more-specifics accept it). Add a route object with origin AS30286 in the RIR database for the space. |
| Route object: none | 192.225.157.0/24 | No route object for it. A route object for 192.225.156.0/22 with origin AS30286 covers it (filters allowing more-specifics accept it). Add a route object with origin AS30286 in the RIR database for the space. |
| Route object: none | 192.225.158.0/24 | No route object for it. A route object for 192.225.156.0/22 with origin AS30286 covers it (filters allowing more-specifics accept it). Add a route object with origin AS30286 in the RIR database for the space. |
| Route object: none | 192.225.159.0/24 | No route object for it. A route object for 192.225.156.0/22 with origin AS30286 covers it (filters allowing more-specifics accept it). Add a route object with origin AS30286 in the RIR database for the space. |
| Route object: none | 199.101.156.0/24 | No route object for it. A route object for 199.101.156.0/23 with origin AS30286 covers it (filters allowing more-specifics accept it). Add a route object with origin AS30286 in the RIR database for the space. |
| Route object: none | 199.101.157.0/24 | No route object for it. A route object for 199.101.156.0/23 with origin AS30286 covers it (filters allowing more-specifics accept it). Add a route object with origin AS30286 in the RIR database for the space. |
| Route object: none | 2a03:7b40:3::/48 | No route object for it. A route object for 2a03:7b40::/32 with origin AS30286 covers it (filters allowing more-specifics accept it). Add a route object with origin AS30286 in the RIR database for the space. |
| Route object: RIR | 91.235.132.0/22 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 145.43.252.0/23 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 185.32.240.0/23 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 185.32.242.0/23 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 192.225.156.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 69.84.176.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 2a03:7b40:2::/48 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 2a03:7b40::/48 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 2a03:7b40:1::/48 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 69.84.177.6/32 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 69.84.177.7/32 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 91.235.135.229/32 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 91.235.135.230/32 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 145.43.252.20/32 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 145.43.252.21/32 | Route object only in RADB. Add it in the RIR database for the space. |
Route objects not announced
Route objects with origin AS30286 whose prefix no peer sees AS30286 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 145.43.252.0/24 | RADB | Valid |
| 145.43.253.0/24 | RADB | Valid |
| 185.32.240.0/22 | RADB | Valid |
| 185.32.240.0/24 | RADB | Valid |
| 185.32.241.0/24 | RADB | Valid |
| 185.32.242.20/32 | RADB | Valid |
| 185.32.242.21/32 | RADB | Valid |
| 199.101.156.0/22 | RADB | No ROA |
| 2a03:7b40::/32 | RADB | No ROA |
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.