Network · data from 2026-11-12
AS393573 Fuse Telecom
Registry name: FUSE - Fuse Telecom LLC, PR · PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS393573, 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.
| 196.12.166.0/24 | No ROA | Other IRR onlyRADB | 667 99% |
| 192.254.110.0/24 | Valid | Other IRR onlyRADB | 668 99% |
| 72.46.140.0/22 | Valid | RIR databaseARIN, RADB | 667 99% |
| 74.85.156.0/23 | Valid | RIR databaseARIN, RADB | 667 99% |
| 172.96.168.0/22 | Valid | RIR databaseARIN, RADB | 667 99% |
| 216.39.232.0/22 | Valid | RIR databaseARIN, RADB | 667 99% |
| 2607:5980::/32 | Valid | RIR databaseARIN, RADB | 631 99% |
AS-SET
PeeringDB's irr_as_set for AS393573: AS393573:RS-ROUTES-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 (AS393573 isn't in the set, or no route object for AS393573 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 | AS393573 in it | Not covered | |
|---|---|---|---|---|---|---|
| AS393573:RS-ROUTES-ALL | 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 5 are in fix.csv.
- ROA: none1
- Route object: RIR2
- Route object: not announced2
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 196.12.166.0/24 | No ROA covers it. Add a ROA for AS393573, maxLength 24. |
| Route object: RIR | 196.12.166.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 192.254.110.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
Route objects not announced
Route objects with origin AS393573 whose prefix no peer sees AS393573 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 67.230.115.0/24 | RADB | No ROA |
| 198.12.166.0/24 | 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.