bgpreport

Network · data from 2026-11-12

AS328583 Crazyweb Tech

Registry name: CRAZYWEB TECH (PTY) LTD - CRAZYWEB TECH (PTY) LTD, ZA · PeeringDB

24IPv4 routes 87.5% RPKI valid · 91.7% with a route object
1IPv6 routes 100.0% RPKI valid · 100.0% with a route object
3RPKI invalid 3 origin · 0 maxLength
0No ROA 2 with no route object for this origin
3Low visibility seen by under 10% of full-table peers
0Route objects not announced registered with origin AS328583, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS328583, 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.
102.36.198.0/23 Invalid: origin Nonecovered by 102.36.196.0/22 2 0%low visibility 1
102.36.199.0/24 Invalid: origin Nonecovered by 102.36.196.0/22 2 0%low visibility 1
102.36.196.0/22 Invalid: origin RIR databaseAFRINIC 2 0%low visibility 1
102.36.140.0/22 Valid RIR databaseAFRINIC 673 100% 67
102.36.140.0/23 Valid RIR databaseAFRINIC 673 100% 67
102.36.140.0/24 Valid RIR databaseAFRINIC 673 100% 67
102.36.141.0/24 Valid RIR databaseAFRINIC 673 100% 67
102.36.142.0/23 Valid RIR databaseAFRINIC 673 100% 67
102.36.142.0/24 Valid RIR databaseAFRINIC 673 100% 67
102.36.143.0/24 Valid RIR databaseAFRINIC 673 100% 67
102.206.220.0/22 Valid RIR databaseAFRINIC 673 100% 67
102.206.220.0/23 Valid RIR databaseAFRINIC 673 100% 67
102.206.220.0/24 Valid RIR databaseAFRINIC 673 100% 67
102.206.221.0/24 Valid RIR databaseAFRINIC 673 100% 67
102.206.222.0/23 Valid RIR databaseAFRINIC 673 100% 67
102.206.222.0/24 Valid RIR databaseAFRINIC 673 100% 67
102.206.223.0/24 Valid RIR databaseAFRINIC 673 100% 67
102.213.148.0/22 Valid RIR databaseAFRINIC 673 100% 67
102.213.148.0/23 Valid RIR databaseAFRINIC 673 100% 67
102.213.148.0/24 Valid RIR databaseAFRINIC 673 100% 67
102.213.149.0/24 Valid RIR databaseAFRINIC 673 100% 67
102.213.150.0/23 Valid RIR databaseAFRINIC 673 100% 67
102.213.150.0/24 Valid RIR databaseAFRINIC 673 100% 67
102.213.151.0/24 Valid RIR databaseAFRINIC 673 100% 67
2c0f:6140::/32 Valid RIR databaseAFRINIC 634 100% 67

AS-SET

PeeringDB's irr_as_set for AS328583: AS-CRAZYWEB. Expanded from the day's IRR dumps the way bgpq4 does against whois.radb.net: a name with a database is read from that database only, one without from the first database in RADB's order. "Not covered" = this network's own routes that a filter built from the set would leave out (AS328583 isn't in the set, or no route object for AS328583 covers the route; more-specifics of a route object are accepted down to /24 and /48, as with bgpq4 -A -R 24 / -R 48). Customers' routes aren't counted: the collectors show each route's origin, not which network it came through.

NameDatabaseASNsSets Route objectsAS328583 in itNot covered
AS-CRAZYWEB AFRINIC 1123 Yes 0

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: origin3
  • Route object: none2
ChangePrefix or setDetailFull-table peers
ROA: origin102.36.198.0/23ROAs covering it name AS328521, not AS328583. If AS328583 should announce it, add a ROA for AS328583.2 of 673
Route object: none102.36.198.0/23No route object for it. A route object for 102.36.196.0/22 with origin AS328583 covers it (filters allowing more-specifics accept it). Add a route object with origin AS328583 in the RIR database for the space.2 of 673
ROA: origin102.36.199.0/24ROAs covering it name AS328521, not AS328583. If AS328583 should announce it, add a ROA for AS328583.2 of 673
Route object: none102.36.199.0/24No route object for it. A route object for 102.36.196.0/22 with origin AS328583 covers it (filters allowing more-specifics accept it). Add a route object with origin AS328583 in the RIR database for the space.2 of 673
ROA: origin102.36.196.0/22ROAs covering it name AS328521, not AS328583. If AS328583 should announce it, add a ROA for AS328583.2 of 673

Route objects not announced

Every route object with origin AS328583 is announced.

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.