Network · data from 2026-11-12
AS262403 NetWay Telecom
Registry name: AS262403 - Net Way Telecom LTDA ME, BR · PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS262403, 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.
| 2804:3e0:8::/46 | Valid | Nonecovered by 2804:3e0::/34 | 77 12% |
| 177.38.100.0/22 | Valid | Nonecovered by 177.38.96.0/21 | 71 11% |
| 177.38.98.0/24 | Valid | Nonecovered by 177.38.98.0/23 | 1 0%low visibility |
| 177.38.99.0/24 | Valid | Nonecovered by 177.38.98.0/23 | 1 0%low visibility |
| 177.38.100.0/24 | Valid | Nonecovered by 177.38.100.0/23 | 1 0%low visibility |
| 177.38.101.0/24 | Valid | Nonecovered by 177.38.100.0/23 | 1 0%low visibility |
| 177.38.102.0/24 | Valid | Nonecovered by 177.38.102.0/23 | 1 0%low visibility |
| 177.38.103.0/24 | Valid | Nonecovered by 177.38.102.0/23 | 1 0%low visibility |
| 187.85.63.0/24 | Valid | Nonecovered by 187.85.62.0/23 | 1 0%low visibility |
| 177.38.96.0/21 | Valid | Other IRR onlyNTTCOM, RADB, TC | 671 100% |
| 187.61.88.0/22 | Valid | Other IRR onlyNTTCOM, RADB | 671 100% |
| 187.85.60.0/22 | Valid | Other IRR onlyNTTCOM, RADB, TC | 671 100% |
| 2804:3e0::/32 | Valid | Other IRR onlyNTTCOM, RADB, TC | 631 99% |
| 2804:3e0:100::/40 | Valid | Other IRR onlyRADB | 77 12% |
| 2804:3e0:200::/40 | Valid | Other IRR onlyRADB | 77 12% |
| 177.38.96.0/22 | Valid | Other IRR onlyTC | 71 11% |
| 187.61.88.0/23 | Valid | Other IRR onlyRADB | 71 11% |
| 187.61.90.0/23 | Valid | Other IRR onlyRADB | 71 11% |
| 187.85.60.0/23 | Valid | Other IRR onlyRADB | 71 11% |
| 187.85.62.0/23 | Valid | Other IRR onlyRADB | 71 11% |
| 177.38.96.0/23 | Valid | Other IRR onlyTC | 17 3%low visibility |
| 177.38.98.0/23 | Valid | Other IRR onlyRADB, TC | 17 3%low visibility |
| 177.38.100.0/23 | Valid | Other IRR onlyRADB | 17 3%low visibility |
| 177.38.102.0/23 | Valid | Other IRR onlyRADB | 17 3%low visibility |
| 177.38.96.0/24 | Valid | Other IRR onlyRADB | 1 0%low visibility |
| 177.38.97.0/24 | Valid | Other IRR onlyRADB | 1 0%low visibility |
| 187.61.88.0/24 | Valid | Other IRR onlyRADB | 1 0%low visibility |
| 187.61.89.0/24 | Valid | Other IRR onlyRADB | 1 0%low visibility |
| 187.61.90.0/24 | Valid | Other IRR onlyRADB | 1 0%low visibility |
| 187.61.91.0/24 | Valid | Other IRR onlyRADB | 1 0%low visibility |
| 187.85.60.0/24 | Valid | Other IRR onlyRADB | 1 0%low visibility |
| 187.85.61.0/24 | Valid | Other IRR onlyRADB | 1 0%low visibility |
| 187.85.62.0/24 | Valid | Other IRR onlyRADB | 1 0%low visibility |
AS-SET
PeeringDB's irr_as_set for AS262403: AS-GLOBAL-NETWAY. 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 (AS262403 isn't in the set, or no route object for AS262403 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 | AS262403 in it | Not covered |
|---|---|---|---|---|---|
| AS-GLOBAL-NETWAY | RADB1 member set in no database: AS262403:AS-CUSTOMERS-NETWAY | 20 | 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 42 are in fix.csv.
- Route object: none9
- Route object: RIR24
- AS-SET: missing member1
- Route object: not announced8
| Change | Prefix or set | Detail |
|---|---|---|
| Route object: none | 2804:3e0:8::/46 | No route object for it. A route object for 2804:3e0::/34 with origin AS262403 covers it (filters allowing more-specifics accept it). Add a route object with origin AS262403 in the RIR database for the space. |
| Route object: none | 177.38.100.0/22 | No route object for it. A route object for 177.38.96.0/21 with origin AS262403 covers it (filters allowing more-specifics accept it). Add a route object with origin AS262403 in the RIR database for the space. |
| Route object: none | 177.38.98.0/24 | No route object for it. A route object for 177.38.98.0/23 with origin AS262403 covers it (filters allowing more-specifics accept it). Add a route object with origin AS262403 in the RIR database for the space. |
| Route object: none | 177.38.99.0/24 | No route object for it. A route object for 177.38.98.0/23 with origin AS262403 covers it (filters allowing more-specifics accept it). Add a route object with origin AS262403 in the RIR database for the space. |
| Route object: none | 177.38.100.0/24 | No route object for it. A route object for 177.38.100.0/23 with origin AS262403 covers it (filters allowing more-specifics accept it). Add a route object with origin AS262403 in the RIR database for the space. |
| Route object: none | 177.38.101.0/24 | No route object for it. A route object for 177.38.100.0/23 with origin AS262403 covers it (filters allowing more-specifics accept it). Add a route object with origin AS262403 in the RIR database for the space. |
| Route object: none | 177.38.102.0/24 | No route object for it. A route object for 177.38.102.0/23 with origin AS262403 covers it (filters allowing more-specifics accept it). Add a route object with origin AS262403 in the RIR database for the space. |
| Route object: none | 177.38.103.0/24 | No route object for it. A route object for 177.38.102.0/23 with origin AS262403 covers it (filters allowing more-specifics accept it). Add a route object with origin AS262403 in the RIR database for the space. |
| Route object: none | 187.85.63.0/24 | No route object for it. A route object for 187.85.62.0/23 with origin AS262403 covers it (filters allowing more-specifics accept it). Add a route object with origin AS262403 in the RIR database for the space. |
| Route object: RIR | 177.38.96.0/21 | Route object only in NTTCOM, RADB, TC. Add it in the RIR database for the space. |
| Route object: RIR | 187.61.88.0/22 | Route object only in NTTCOM, RADB. Add it in the RIR database for the space. |
| Route object: RIR | 187.85.60.0/22 | Route object only in NTTCOM, RADB, TC. Add it in the RIR database for the space. |
| Route object: RIR | 2804:3e0::/32 | Route object only in NTTCOM, RADB, TC. Add it in the RIR database for the space. |
| Route object: RIR | 2804:3e0:100::/40 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 2804:3e0:200::/40 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 177.38.96.0/22 | Route object only in TC. Add it in the RIR database for the space. |
| Route object: RIR | 187.61.88.0/23 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 187.61.90.0/23 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 187.85.60.0/23 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 187.85.62.0/23 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 177.38.96.0/23 | Route object only in TC. Add it in the RIR database for the space. |
| Route object: RIR | 177.38.98.0/23 | Route object only in RADB, TC. Add it in the RIR database for the space. |
| Route object: RIR | 177.38.100.0/23 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 177.38.102.0/23 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 177.38.96.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 177.38.97.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 187.61.88.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 187.61.89.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 187.61.90.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 187.61.91.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 187.85.60.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 187.85.61.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 187.85.62.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| AS-SET: missing member | AS-GLOBAL-NETWAY | AS-GLOBAL-NETWAY (RADB) lists AS262403:AS-CUSTOMERS-NETWAY; no IRR database read has it. |
Route objects not announced
Route objects with origin AS262403 whose prefix no peer sees AS262403 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 187.85.66.0/24 | RADB | No ROA |
| 2804:3e0::/33 | RADB | Valid |
| 2804:3e0::/34 | RADB | Valid |
| 2804:3e0:4000::/34 | RADB | Valid |
| 2804:3e0:8000::/33 | RADB | Valid |
| 2804:3e0:8000::/34 | RADB | Valid |
| 2804:3e0:c000::/34 | RADB | Valid |
| 2804:3e0:ffff::/48 | RADB | 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.