Network · data from 2026-11-12
AS267809 360NET
Registry name: AS267809 - 360NET C.A., VE · PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS267809, 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.
| 45.173.196.0/24 | Valid | Other IRR onlyRADB | 668 99% |
| 45.173.197.0/24 | Valid | Other IRR onlyRADB | 668 99% |
| 45.173.198.0/24 | Valid | Other IRR onlyRADB | 668 99% |
| 45.173.199.0/24 | Valid | Other IRR onlyRADB | 668 99% |
| 82.86.116.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 82.86.112.0/21 | Valid | RIR databaseRIPE | 670 100% |
| 82.86.112.0/24 | Valid | RIR databaseRIPE | 668 99% |
| 82.86.113.0/24 | Valid | RIR databaseRIPE | 668 99% |
| 82.86.114.0/24 | Valid | RIR databaseRIPE | 668 99% |
| 82.86.115.0/24 | Valid | RIR databaseRIPE | 668 99% |
| 82.86.120.0/24 | Valid | RIR databaseRIPE | 668 99% |
| 82.86.121.0/24 | Valid | RIR databaseRIPE | 668 99% |
| 82.86.122.0/24 | Valid | RIR databaseRIPE | 668 99% |
| 82.86.123.0/24 | Valid | RIR databaseRIPE | 668 99% |
| 2803:1060::/32 | Valid | RIR databaseLACNIC, RADB | 635 100% |
| 45.173.196.0/22 | Valid | RIR databaseLACNIC, RADB | 2 0%low visibility |
AS-SET
PeeringDB's irr_as_set for AS267809: RADB::AS267809:AS-CONE. 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 (AS267809 isn't in the set, or no route object for AS267809 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 | AS267809 in it | Not covered |
|---|---|---|---|---|---|
| RADB::AS267809:AS-CONE | RADB1 member set in no database: AS269738:AS-CUSTOMERS | 18 | 2 | 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 26 are in fix.csv.
- Route object: RIR4
- AS-SET: missing member1
- Route object: not announced21
| Change | Prefix or set | Detail |
|---|---|---|
| Route object: RIR | 45.173.196.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 45.173.197.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 45.173.198.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 45.173.199.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| AS-SET: missing member | RADB::AS267809:AS-CONE | AS267809:AS-CONE (RADB) lists AS269738:AS-CUSTOMERS; no IRR database read has it. |
Route objects not announced
Route objects with origin AS267809 whose prefix no peer sees AS267809 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 82.86.112.0/20 | RADB, RIPE | Valid |
| 82.86.112.0/22 | RIPE | Valid |
| 82.86.112.0/23 | RIPE | Valid |
| 82.86.114.0/23 | RIPE | Valid |
| 82.86.116.0/22 | RIPE | Valid |
| 82.86.116.0/23 | RIPE | Valid |
| 82.86.117.0/24 | RIPE | Valid |
| 82.86.118.0/23 | RIPE | Valid |
| 82.86.118.0/24 | RIPE | Valid |
| 82.86.119.0/24 | RIPE | Valid |
| 82.86.120.0/21 | RIPE | Valid |
| 82.86.120.0/22 | RIPE | Valid |
| 82.86.120.0/23 | RIPE | Valid |
| 82.86.122.0/23 | RIPE | Valid |
| 82.86.124.0/22 | RIPE | Valid |
| 82.86.124.0/23 | RIPE | Valid |
| 82.86.124.0/24 | RIPE | Valid |
| 82.86.125.0/24 | RIPE | Valid |
| 82.86.126.0/23 | RIPE | Valid |
| 82.86.126.0/24 | RIPE | Valid |
| 82.86.127.0/24 | RIPE | Valid |
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.