bgpreport

Network · data from 2026-11-12

AS328045 Multichoice Support Services

Registry name: Multichoice Support Services (Pty) Ltd - Multichoice Support Services (Pty) Ltd, ZA · PeeringDB

5IPv4 routes 80.0% RPKI valid · 80.0% with a route object
0IPv6 routes
1RPKI invalid 1 origin · 0 maxLength
0No ROA 1 with no route object for this origin
1Low visibility seen by under 10% of full-table peers
4Route objects not announced registered with origin AS328045, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS328045, 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.

197.80.203.0/24 Invalid: origin None 55 8%low visibility 23
160.119.80.0/24 Valid RIR databaseAFRINIC 671 100% 67
160.119.81.0/24 Valid RIR databaseAFRINIC 671 100% 67
160.119.82.0/24 Valid RIR databaseAFRINIC 671 100% 67
160.119.83.0/24 Valid RIR databaseAFRINIC, RADB 671 100% 67

AS-SET

AS328045'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 6 are in fix.csv.

  • ROA: origin1
  • Route object: none1
  • Route object: not announced4
ChangePrefix or setDetailFull-table peers
ROA: origin197.80.203.0/24ROAs covering it name AS3741, AS10474, AS20011, not AS328045. If AS328045 should announce it, add a ROA for AS328045.55 of 673
Route object: none197.80.203.0/24No route object for it. Add a route object with origin AS328045 in the RIR database for the space.55 of 673

Route objects not announced

Route objects with origin AS328045 whose prefix no peer sees AS328045 announce. Many are kept on purpose (backup routes, space announced only in some places).

160.119.80.0/22AFRINIC, RADBNo ROA
160.119.82.0/23RADBNo ROA
2c0f:f448:4000::/40RADBValid
2c0f:f448:4800::/40RADBValid

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.