Network · data from 2026-11-12
AS268786 L H FERREIRA ZOBY
Registry name: AS268786 - LINE FIBRA TELECOM LTDA, BR · PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS268786, 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:5aa4::/38 | Valid | Nonecovered by 2804:5aa4::/34 | 636 100% |
| 45.172.170.0/24 | Valid | Other IRR onlyTC | 672 100% |
| 168.196.204.0/23 | Valid | Other IRR onlyTC | 672 100% |
| 168.196.205.0/24 | Valid | Other IRR onlyTC | 672 100% |
| 45.172.169.0/24 | Valid | Other IRR onlyRADB, TC | 671 100% |
| 45.172.171.0/24 | Valid | Other IRR onlyTC | 671 100% |
| 168.196.204.0/24 | Valid | Other IRR onlyTC | 671 100% |
| 45.172.168.0/24 | Valid | Other IRR onlyTC | 670 100% |
| 168.196.206.0/23 | Valid | Other IRR onlyTC | 664 99% |
| 2804:5aa4::/32 | Valid | Other IRR onlyNTTCOM, RADB, TC | 332 52% |
| 168.196.206.0/24 | Valid | Other IRR onlyTC | 57 8%low visibility |
| 168.196.207.0/24 | Valid | Other IRR onlyTC | 57 8%low visibility |
AS-SET
AS268786's PeeringDB record names no AS-SET.
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 22 are in fix.csv.
- Route object: none1
- Route object: RIR11
- Route object: not announced10
| Change | Prefix or set | Detail |
|---|---|---|
| Route object: none | 2804:5aa4::/38 | No route object for it. A route object for 2804:5aa4::/34 with origin AS268786 covers it (filters allowing more-specifics accept it). Add a route object with origin AS268786 in the RIR database for the space. |
| Route object: RIR | 45.172.170.0/24 | Route object only in TC. Add it in the RIR database for the space. |
| Route object: RIR | 168.196.204.0/23 | Route object only in TC. Add it in the RIR database for the space. |
| Route object: RIR | 168.196.205.0/24 | Route object only in TC. Add it in the RIR database for the space. |
| Route object: RIR | 45.172.169.0/24 | Route object only in RADB, TC. Add it in the RIR database for the space. |
| Route object: RIR | 45.172.171.0/24 | Route object only in TC. Add it in the RIR database for the space. |
| Route object: RIR | 168.196.204.0/24 | Route object only in TC. Add it in the RIR database for the space. |
| Route object: RIR | 45.172.168.0/24 | Route object only in TC. Add it in the RIR database for the space. |
| Route object: RIR | 168.196.206.0/23 | Route object only in TC. Add it in the RIR database for the space. |
| Route object: RIR | 2804:5aa4::/32 | Route object only in NTTCOM, RADB, TC. Add it in the RIR database for the space. |
| Route object: RIR | 168.196.206.0/24 | Route object only in TC. Add it in the RIR database for the space. |
| Route object: RIR | 168.196.207.0/24 | Route object only in TC. Add it in the RIR database for the space. |
Route objects not announced
Route objects with origin AS268786 whose prefix no peer sees AS268786 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 45.172.168.0/22 | NTTCOM, RADB, TC | No ROA |
| 45.172.168.0/23 | RADB, TC | No ROA |
| 45.172.170.0/23 | RADB, TC | No ROA |
| 168.196.204.0/22 | NTTCOM, TC | No ROA |
| 2804:5aa4::/33 | RADB, TC | Valid |
| 2804:5aa4::/34 | TC | Valid |
| 2804:5aa4:4000::/34 | TC | Valid |
| 2804:5aa4:8000::/33 | TC | Valid |
| 2804:5aa4:8000::/34 | TC | Valid |
| 2804:5aa4:c000::/34 | 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.