Network · data from 2026-11-12
AS5734 Telkom SA Ltd. - Telkom SA Ltd.
Registry name: Telkom SA Ltd. - Telkom SA Ltd., ZA · not in PeeringDB
11IPv4 routes
0.0% RPKI valid · 27.3% with a route object
0IPv6 routes
0RPKI invalid
0 origin · 0 maxLength
11No ROA
8 with no route object for this origin
0Low visibility
seen by under 10% of full-table peers
6Route objects not announced
registered with origin AS5734, seen from no peer
Announced routes
Every prefix a peer of the route collectors sees with origin AS5734, 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.
| 165.143.0.0/18 | No ROA | Nonecovered by 165.143.0.0/16 | 671 100% |
| 165.143.64.0/19 | No ROA | Nonecovered by 165.143.0.0/16 | 671 100% |
| 165.143.100.0/22 | No ROA | Nonecovered by 165.143.0.0/16 | 671 100% |
| 165.143.104.0/22 | No ROA | Nonecovered by 165.143.0.0/16 | 671 100% |
| 165.143.108.0/24 | No ROA | Nonecovered by 165.143.0.0/16 | 671 100% |
| 165.143.111.0/24 | No ROA | Nonecovered by 165.143.0.0/16 | 671 100% |
| 165.143.112.0/20 | No ROA | Nonecovered by 165.143.0.0/16 | 671 100% |
| 165.143.128.0/17 | No ROA | Nonecovered by 165.143.0.0/16 | 671 100% |
| 198.54.204.0/22 | No ROA | Other IRR onlyNTTCOM, RADB | 671 100% |
| 165.148.30.0/24 | No ROA | Other IRR onlyNTTCOM | 670 100% |
| 165.148.128.0/17 | No ROA | Other IRR onlyNTTCOM | 670 100% |
AS-SET
AS5734 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 28 are in fix.csv.
- ROA: none11
- Route object: none8
- Route object: RIR3
- Route object: not announced6
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 165.143.0.0/18 | No ROA covers it. Add a ROA for AS5734, maxLength 18. |
| Route object: none | 165.143.0.0/18 | No route object for it. A route object for 165.143.0.0/16 with origin AS5734 covers it (filters allowing more-specifics accept it). Add a route object with origin AS5734 in the RIR database for the space. |
| ROA: none | 165.143.64.0/19 | No ROA covers it. Add a ROA for AS5734, maxLength 19. |
| Route object: none | 165.143.64.0/19 | No route object for it. A route object for 165.143.0.0/16 with origin AS5734 covers it (filters allowing more-specifics accept it). Add a route object with origin AS5734 in the RIR database for the space. |
| ROA: none | 165.143.100.0/22 | No ROA covers it. Add a ROA for AS5734, maxLength 22. |
| Route object: none | 165.143.100.0/22 | No route object for it. A route object for 165.143.0.0/16 with origin AS5734 covers it (filters allowing more-specifics accept it). Add a route object with origin AS5734 in the RIR database for the space. |
| ROA: none | 165.143.104.0/22 | No ROA covers it. Add a ROA for AS5734, maxLength 22. |
| Route object: none | 165.143.104.0/22 | No route object for it. A route object for 165.143.0.0/16 with origin AS5734 covers it (filters allowing more-specifics accept it). Add a route object with origin AS5734 in the RIR database for the space. |
| ROA: none | 165.143.108.0/24 | No ROA covers it. Add a ROA for AS5734, maxLength 24. |
| Route object: none | 165.143.108.0/24 | No route object for it. A route object for 165.143.0.0/16 with origin AS5734 covers it (filters allowing more-specifics accept it). Add a route object with origin AS5734 in the RIR database for the space. |
| ROA: none | 165.143.111.0/24 | No ROA covers it. Add a ROA for AS5734, maxLength 24. |
| Route object: none | 165.143.111.0/24 | No route object for it. A route object for 165.143.0.0/16 with origin AS5734 covers it (filters allowing more-specifics accept it). Add a route object with origin AS5734 in the RIR database for the space. |
| ROA: none | 165.143.112.0/20 | No ROA covers it. Add a ROA for AS5734, maxLength 20. |
| Route object: none | 165.143.112.0/20 | No route object for it. A route object for 165.143.0.0/16 with origin AS5734 covers it (filters allowing more-specifics accept it). Add a route object with origin AS5734 in the RIR database for the space. |
| ROA: none | 165.143.128.0/17 | No ROA covers it. Add a ROA for AS5734, maxLength 17. |
| Route object: none | 165.143.128.0/17 | No route object for it. A route object for 165.143.0.0/16 with origin AS5734 covers it (filters allowing more-specifics accept it). Add a route object with origin AS5734 in the RIR database for the space. |
| ROA: none | 198.54.204.0/22 | No ROA covers it. Add a ROA for AS5734, maxLength 22. |
| Route object: RIR | 198.54.204.0/22 | Route object only in NTTCOM, RADB. Add it in the RIR database for the space. |
| ROA: none | 165.148.30.0/24 | No ROA covers it. Add a ROA for AS5734, maxLength 24. |
| Route object: RIR | 165.148.30.0/24 | Route object only in NTTCOM. Add it in the RIR database for the space. |
| ROA: none | 165.148.128.0/17 | No ROA covers it. Add a ROA for AS5734, maxLength 17. |
| Route object: RIR | 165.148.128.0/17 | Route object only in NTTCOM. Add it in the RIR database for the space. |
Route objects not announced
Route objects with origin AS5734 whose prefix no peer sees AS5734 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 165.143.0.0/16 | NTTCOM, RADB | No ROA |
| 196.1.84.0/24 | NTTCOM, RADB | No ROA |
| 198.54.204.0/24 | NTTCOM | No ROA |
| 198.54.205.0/24 | NTTCOM | No ROA |
| 198.54.206.0/24 | NTTCOM | No ROA |
| 198.54.208.0/24 | NTTCOM, 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.