Network · data from 2026-11-12
AS262374 FAZZY INTERNET
Registry name: AS262374 - FAZZY INTERNET, BR · PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS262374, 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.
| 170.254.119.0/24 | Valid | Nonecovered by 170.254.118.0/23 | 6 1%low visibility |
| 177.128.165.0/24 | Valid | Other IRR onlyTC | 671 100% |
| 138.99.244.0/22 | Valid | Other IRR onlyNTTCOM, RADB, TC | 669 99% |
| 177.39.24.0/22 | Valid | Other IRR onlyNTTCOM, RADB, TC | 669 99% |
| 177.128.160.0/21 | Valid | Other IRR onlyNTTCOM, RADB, TC | 669 99% |
| 177.128.164.0/22 | Valid | Other IRR onlyNTTCOM, RADB, TC | 669 99% |
| 179.127.120.0/22 | Valid | Other IRR onlyNTTCOM, RADB, TC | 669 99% |
| 170.254.116.0/22 | Valid | Other IRR onlyNTTCOM, RADB, TC | 668 99% |
| 177.128.160.0/22 | Valid | Other IRR onlyNTTCOM, RADB, TC | 668 99% |
| 2804:878::/32 | Valid | Other IRR onlyNTTCOM, RADB, TC | 633 100% |
| 177.128.164.0/24 | Valid | Other IRR onlyTC | 8 1%low visibility |
| 177.128.166.0/24 | Valid | Other IRR onlyRADB, TC | 8 1%low visibility |
| 138.99.244.0/23 | Valid | Other IRR onlyTC | 7 1%low visibility |
| 138.99.246.0/23 | Valid | Other IRR onlyTC | 7 1%low visibility |
| 170.254.116.0/23 | Valid | Other IRR onlyTC | 7 1%low visibility |
| 170.254.118.0/23 | Valid | Other IRR onlyTC | 7 1%low visibility |
| 177.39.24.0/23 | Valid | Other IRR onlyTC | 7 1%low visibility |
| 177.39.26.0/23 | Valid | Other IRR onlyTC | 7 1%low visibility |
| 177.128.160.0/23 | Valid | Other IRR onlyTC | 7 1%low visibility |
| 177.128.162.0/23 | Valid | Other IRR onlyTC | 7 1%low visibility |
| 177.128.164.0/23 | Valid | Other IRR onlyTC | 7 1%low visibility |
| 177.128.166.0/23 | Valid | Other IRR onlyTC | 7 1%low visibility |
| 179.127.120.0/23 | Valid | Other IRR onlyTC | 7 1%low visibility |
| 179.127.122.0/23 | Valid | Other IRR onlyTC | 7 1%low visibility |
| 138.99.244.0/24 | Valid | Other IRR onlyTC | 6 1%low visibility |
| 138.99.245.0/24 | Valid | Other IRR onlyTC | 6 1%low visibility |
| 138.99.246.0/24 | Valid | Other IRR onlyTC | 6 1%low visibility |
| 138.99.247.0/24 | Valid | Other IRR onlyTC | 6 1%low visibility |
| 170.254.116.0/24 | Valid | Other IRR onlyTC | 6 1%low visibility |
| 170.254.117.0/24 | Valid | Other IRR onlyTC | 6 1%low visibility |
| 170.254.118.0/24 | Valid | Other IRR onlyTC | 6 1%low visibility |
| 177.39.24.0/24 | Valid | Other IRR onlyTC | 6 1%low visibility |
| 177.39.25.0/24 | Valid | Other IRR onlyTC | 6 1%low visibility |
| 177.39.26.0/24 | Valid | Other IRR onlyTC | 6 1%low visibility |
| 177.39.27.0/24 | Valid | Other IRR onlyTC | 6 1%low visibility |
| 177.128.160.0/24 | Valid | Other IRR onlyTC | 6 1%low visibility |
| 177.128.161.0/24 | Valid | Other IRR onlyTC | 6 1%low visibility |
| 177.128.162.0/24 | Valid | Other IRR onlyTC | 6 1%low visibility |
| 177.128.163.0/24 | Valid | Other IRR onlyTC | 6 1%low visibility |
| 177.128.167.0/24 | Valid | Other IRR onlyTC | 6 1%low visibility |
| 179.127.120.0/24 | Valid | Other IRR onlyTC | 6 1%low visibility |
| 179.127.121.0/24 | Valid | Other IRR onlyTC | 6 1%low visibility |
| 179.127.122.0/24 | Valid | Other IRR onlyTC | 6 1%low visibility |
| 179.127.123.0/24 | Valid | Other IRR onlyTC | 6 1%low visibility |
| 2804:878::/33 | Valid | Other IRR onlyNTTCOM, TC | 1 0%low visibility |
| 2804:878::/34 | Valid | Other IRR onlyTC | 1 0%low visibility |
| 2804:878::/35 | Valid | Other IRR onlyTC | 1 0%low visibility |
| 2804:878:8000::/33 | Valid | Other IRR onlyNTTCOM, TC | 1 0%low visibility |
| 2804:878:8000::/34 | Valid | Other IRR onlyTC | 1 0%low visibility |
| 2804:878:8000::/35 | Valid | Other IRR onlyTC | 1 0%low visibility |
AS-SET
PeeringDB's irr_as_set for AS262374: AS-FAZZYBR. 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 (AS262374 isn't in the set, or no route object for AS262374 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 | AS262374 in it | Not covered |
|---|---|---|---|---|---|
| AS-FAZZYBR | NTTCOM | 8 | 1 | Yes | 0 |
| TC (also) | 8 | 1 | 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 56 are in fix.csv.
- Route object: none1
- Route object: RIR49
- Route object: not announced6
| Change | Prefix or set | Detail |
|---|---|---|
| Route object: none | 170.254.119.0/24 | No route object for it. A route object for 170.254.118.0/23 with origin AS262374 covers it (filters allowing more-specifics accept it). Add a route object with origin AS262374 in the RIR database for the space. |
| Route object: RIR | 177.128.165.0/24 | Route object only in TC. Add it in the RIR database for the space. |
| Route object: RIR | 138.99.244.0/22 | Route object only in NTTCOM, RADB, TC. Add it in the RIR database for the space. |
| Route object: RIR | 177.39.24.0/22 | Route object only in NTTCOM, RADB, TC. Add it in the RIR database for the space. |
| Route object: RIR | 177.128.160.0/21 | Route object only in NTTCOM, RADB, TC. Add it in the RIR database for the space. |
| Route object: RIR | 177.128.164.0/22 | Route object only in NTTCOM, RADB, TC. Add it in the RIR database for the space. |
| Route object: RIR | 179.127.120.0/22 | Route object only in NTTCOM, RADB, TC. Add it in the RIR database for the space. |
| Route object: RIR | 170.254.116.0/22 | Route object only in NTTCOM, RADB, TC. Add it in the RIR database for the space. |
| Route object: RIR | 177.128.160.0/22 | Route object only in NTTCOM, RADB, TC. Add it in the RIR database for the space. |
| Route object: RIR | 2804:878::/32 | Route object only in NTTCOM, RADB, TC. Add it in the RIR database for the space. |
| Route object: RIR | 177.128.164.0/24 | Route object only in TC. Add it in the RIR database for the space. |
| Route object: RIR | 177.128.166.0/24 | Route object only in RADB, TC. Add it in the RIR database for the space. |
| Route object: RIR | 138.99.244.0/23 | Route object only in TC. Add it in the RIR database for the space. |
| Route object: RIR | 138.99.246.0/23 | Route object only in TC. Add it in the RIR database for the space. |
| Route object: RIR | 170.254.116.0/23 | Route object only in TC. Add it in the RIR database for the space. |
| Route object: RIR | 170.254.118.0/23 | Route object only in TC. Add it in the RIR database for the space. |
| Route object: RIR | 177.39.24.0/23 | Route object only in TC. Add it in the RIR database for the space. |
| Route object: RIR | 177.39.26.0/23 | Route object only in TC. Add it in the RIR database for the space. |
| Route object: RIR | 177.128.160.0/23 | Route object only in TC. Add it in the RIR database for the space. |
| Route object: RIR | 177.128.162.0/23 | Route object only in TC. Add it in the RIR database for the space. |
| Route object: RIR | 177.128.164.0/23 | Route object only in TC. Add it in the RIR database for the space. |
| Route object: RIR | 177.128.166.0/23 | Route object only in TC. Add it in the RIR database for the space. |
| Route object: RIR | 179.127.120.0/23 | Route object only in TC. Add it in the RIR database for the space. |
| Route object: RIR | 179.127.122.0/23 | Route object only in TC. Add it in the RIR database for the space. |
| Route object: RIR | 138.99.244.0/24 | Route object only in TC. Add it in the RIR database for the space. |
| Route object: RIR | 138.99.245.0/24 | Route object only in TC. Add it in the RIR database for the space. |
| Route object: RIR | 138.99.246.0/24 | Route object only in TC. Add it in the RIR database for the space. |
| Route object: RIR | 138.99.247.0/24 | Route object only in TC. Add it in the RIR database for the space. |
| Route object: RIR | 170.254.116.0/24 | Route object only in TC. Add it in the RIR database for the space. |
| Route object: RIR | 170.254.117.0/24 | Route object only in TC. Add it in the RIR database for the space. |
| Route object: RIR | 170.254.118.0/24 | Route object only in TC. Add it in the RIR database for the space. |
| Route object: RIR | 177.39.24.0/24 | Route object only in TC. Add it in the RIR database for the space. |
| Route object: RIR | 177.39.25.0/24 | Route object only in TC. Add it in the RIR database for the space. |
| Route object: RIR | 177.39.26.0/24 | Route object only in TC. Add it in the RIR database for the space. |
| Route object: RIR | 177.39.27.0/24 | Route object only in TC. Add it in the RIR database for the space. |
| Route object: RIR | 177.128.160.0/24 | Route object only in TC. Add it in the RIR database for the space. |
| Route object: RIR | 177.128.161.0/24 | Route object only in TC. Add it in the RIR database for the space. |
| Route object: RIR | 177.128.162.0/24 | Route object only in TC. Add it in the RIR database for the space. |
| Route object: RIR | 177.128.163.0/24 | Route object only in TC. Add it in the RIR database for the space. |
| Route object: RIR | 177.128.167.0/24 | Route object only in TC. Add it in the RIR database for the space. |
| Route object: RIR | 179.127.120.0/24 | Route object only in TC. Add it in the RIR database for the space. |
| Route object: RIR | 179.127.121.0/24 | Route object only in TC. Add it in the RIR database for the space. |
| Route object: RIR | 179.127.122.0/24 | Route object only in TC. Add it in the RIR database for the space. |
| Route object: RIR | 179.127.123.0/24 | Route object only in TC. Add it in the RIR database for the space. |
| Route object: RIR | 2804:878::/33 | Route object only in NTTCOM, TC. Add it in the RIR database for the space. |
| Route object: RIR | 2804:878::/34 | Route object only in TC. Add it in the RIR database for the space. |
| Route object: RIR | 2804:878::/35 | Route object only in TC. Add it in the RIR database for the space. |
| Route object: RIR | 2804:878:8000::/33 | Route object only in NTTCOM, TC. Add it in the RIR database for the space. |
| Route object: RIR | 2804:878:8000::/34 | Route object only in TC. Add it in the RIR database for the space. |
| Route object: RIR | 2804:878:8000::/35 | Route object only in TC. Add it in the RIR database for the space. |
Route objects not announced
Route objects with origin AS262374 whose prefix no peer sees AS262374 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 2804:878::/36 | TC | Valid |
| 2804:878::/48 | NTTCOM | Valid |
| 2804:878:1::/48 | NTTCOM | Valid |
| 2804:878:1c0::/48 | RADB, TC | Valid |
| 2804:878:8000::/36 | TC | Valid |
| 2804:878:cace::/48 | NTTCOM, TC | 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.