bgpreport

Network · data from 2026-11-12

AS327980 FASTHOSTING (PTY) LTD - FASTHOSTING (PTY) LTD

Registry name: FASTHOSTING (PTY) LTD - FASTHOSTING (PTY) LTD, ZA · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS327980, 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.
2c0f:f570::/32 No ROA RIR databaseAFRINIC 634 100% 67
41.216.183.0/24 Valid RIR databaseAFRINIC 670 100% 67
41.216.178.0/24 Valid RIR databaseAFRINIC 11 2%low visibility 4
41.216.180.0/24 Valid RIR databaseAFRINIC 11 2%low visibility 4
41.216.186.0/24 Valid RIR databaseAFRINIC, RADB 11 2%low visibility 4
41.216.190.0/24 Valid RIR databaseAFRINIC, RADB 11 2%low visibility 4
41.216.191.0/24 Valid RIR databaseAFRINIC, RADB 11 2%low visibility 4
41.216.182.0/24 Valid RIR databaseAFRINIC 9 1%low visibility 2

AS-SET

AS327980 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 5 are in fix.csv.

  • ROA: none1
  • Route object: not announced4
ChangePrefix or setDetailFull-table peers
ROA: none2c0f:f570::/32No ROA covers it. Add a ROA for AS327980, maxLength 32.634 of 636

Route objects not announced

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

41.216.177.0/24AFRINICValid
41.216.181.0/24AFRINICValid
41.216.185.0/24AFRINICInvalid: origin
41.216.188.0/24AFRINICValid

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.