Network · data from 2026-11-12
AS327808 TESUCO TELECOMMUNICATIONS (PTY) LTD - TESUCO TELECOMMUNICATIONS (PTY) LTD
Registry name: TESUCO TELECOMMUNICATIONS (PTY) LTD - TESUCO TELECOMMUNICATIONS (PTY) LTD, ZA · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS327808, 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.46.23.0/24 | No ROA | Other origin only | 229 34% |
| 154.73.181.0/24 | No ROA | Other IRR onlyRADB, RIPE-NONAUTH | 672 100% |
| 154.73.182.0/24 | No ROA | Other IRR onlyRADB, RIPE-NONAUTH | 672 100% |
| 154.73.183.0/24 | No ROA | Other IRR onlyRADB, RIPE-NONAUTH | 672 100% |
| 154.73.180.0/24 | No ROA | Other IRR onlyRADB, RIPE-NONAUTH | 671 100% |
| 102.130.96.0/24 | No ROA | RIR databaseAFRINIC, RADB | 672 100% |
| 165.16.240.0/20 | No ROA | RIR databaseAFRINIC, RADB, RIPE-NONAUTH | 672 100% |
| 2c0f:4940::/32 | No ROA | RIR databaseAFRINIC | 634 100% |
AS-SET
AS327808 isn't in PeeringDB, where networks name their 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 32 are in fix.csv.
- ROA: none8
- Route object: none1
- Route object: RIR4
- Route object: not announced19
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 196.46.23.0/24 | No ROA covers it. Add a ROA for AS327808, maxLength 24. |
| Route object: none | 196.46.23.0/24 | Route objects for it name AS6421, AS16637, AS36937, AS37180. Add a route object with origin AS327808 in the RIR database for the space. |
| ROA: none | 154.73.181.0/24 | No ROA covers it. Add a ROA for AS327808, maxLength 24. |
| Route object: RIR | 154.73.181.0/24 | Route object only in RADB, RIPE-NONAUTH. Add it in the RIR database for the space. |
| ROA: none | 154.73.182.0/24 | No ROA covers it. Add a ROA for AS327808, maxLength 24. |
| Route object: RIR | 154.73.182.0/24 | Route object only in RADB, RIPE-NONAUTH. Add it in the RIR database for the space. |
| ROA: none | 154.73.183.0/24 | No ROA covers it. Add a ROA for AS327808, maxLength 24. |
| Route object: RIR | 154.73.183.0/24 | Route object only in RADB, RIPE-NONAUTH. Add it in the RIR database for the space. |
| ROA: none | 154.73.180.0/24 | No ROA covers it. Add a ROA for AS327808, maxLength 24. |
| Route object: RIR | 154.73.180.0/24 | Route object only in RADB, RIPE-NONAUTH. Add it in the RIR database for the space. |
| ROA: none | 102.130.96.0/24 | No ROA covers it. Add a ROA for AS327808, maxLength 24. |
| ROA: none | 165.16.240.0/20 | No ROA covers it. Add a ROA for AS327808, maxLength 20. |
| ROA: none | 2c0f:4940::/32 | No ROA covers it. Add a ROA for AS327808, maxLength 32. |
Route objects not announced
Route objects with origin AS327808 whose prefix no peer sees AS327808 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 154.73.180.0/22 | AFRINIC, RADB, RIPE-NONAUTH | No ROA |
| 165.16.240.0/24 | AFRINIC, RADB, RIPE-NONAUTH | No ROA |
| 165.16.241.0/24 | AFRINIC, RADB, RIPE-NONAUTH | No ROA |
| 165.16.242.0/24 | AFRINIC, RADB, RIPE-NONAUTH | No ROA |
| 165.16.243.0/24 | AFRINIC, RADB, RIPE-NONAUTH | No ROA |
| 165.16.244.0/24 | AFRINIC, RADB, RIPE-NONAUTH | No ROA |
| 165.16.245.0/24 | AFRINIC, RADB, RIPE-NONAUTH | No ROA |
| 165.16.246.0/24 | AFRINIC, RADB, RIPE-NONAUTH | No ROA |
| 165.16.247.0/24 | AFRINIC, RADB, RIPE-NONAUTH | No ROA |
| 165.16.248.0/21 | AFRINIC, RADB | No ROA |
| 165.16.248.0/24 | AFRINIC, RADB, RIPE-NONAUTH | No ROA |
| 165.16.249.0/24 | AFRINIC, RADB, RIPE-NONAUTH | No ROA |
| 165.16.250.0/24 | AFRINIC, RADB, RIPE-NONAUTH | No ROA |
| 165.16.251.0/24 | AFRINIC, RADB, RIPE-NONAUTH | No ROA |
| 165.16.252.0/22 | AFRINIC, RADB | No ROA |
| 165.16.252.0/24 | RADB, RIPE-NONAUTH | No ROA |
| 165.16.253.0/24 | RADB, RIPE-NONAUTH | No ROA |
| 165.16.254.0/24 | RADB, RIPE-NONAUTH | No ROA |
| 165.16.255.0/24 | RADB, RIPE-NONAUTH | 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.