bgpreport

Network · data from 2026-11-12

AS328576 TelcoExchange (aka AS328576.net)

Registry name: Surf4Life Pty (LTD) - Surf4Life Pty (LTD), ZA · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS328576, 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.22.240.0/21 Valid RIR databaseAFRINIC 672 100% 67
102.22.240.0/24 Valid RIR databaseAFRINIC 672 100% 67
102.22.243.0/24 Valid RIR databaseAFRINIC 672 100% 67
102.22.245.0/24 Valid RIR databaseAFRINIC 672 100% 67
102.22.247.0/24 Valid RIR databaseAFRINIC 672 100% 67
102.218.156.0/22 Valid RIR databaseAFRINIC 672 100% 67
102.218.156.0/24 Valid RIR databaseAFRINIC 672 100% 67
102.218.157.0/24 Valid RIR databaseAFRINIC 672 100% 67
102.218.158.0/24 Valid RIR databaseAFRINIC 672 100% 67
102.218.159.0/24 Valid RIR databaseAFRINIC 672 100% 67
102.219.60.0/22 Valid RIR databaseAFRINIC 672 100% 67
102.219.61.0/24 Valid RIR databaseAFRINIC 672 100% 67
102.219.62.0/24 Valid RIR databaseAFRINIC 672 100% 67
102.219.63.0/24 Valid RIR databaseAFRINIC 672 100% 67
102.220.60.0/24 Valid RIR databaseAFRINIC 672 100% 67
102.220.61.0/24 Valid RIR databaseAFRINIC 672 100% 67
102.221.200.0/22 Valid RIR databaseAFRINIC 672 100% 67
102.221.200.0/24 Valid RIR databaseAFRINIC 672 100% 67
102.221.201.0/24 Valid RIR databaseAFRINIC 672 100% 67
102.221.202.0/24 Valid RIR databaseAFRINIC 672 100% 67
102.221.203.0/24 Valid RIR databaseAFRINIC 672 100% 67
2c0f:eb48::/32 Valid RIR databaseAFRINIC 634 100% 67
2c0f:eb48::/36 Valid RIR databaseAFRINIC 634 100% 67
2c0f:eb48:3000::/36 Valid RIR databaseAFRINIC 634 100% 67
2c0f:eb48:4000::/36 Valid RIR databaseAFRINIC 634 100% 67
2c0f:eb48:5000::/36 Valid RIR databaseAFRINIC 634 100% 67
2c0f:eb48:6000::/36 Valid RIR databaseAFRINIC 634 100% 67
2c0f:eb48:8000::/36 Valid RIR databaseAFRINIC 634 100% 67
2c0f:eb48:9000::/36 Valid RIR databaseAFRINIC 634 100% 67
2c0f:eb48:a000::/36 Valid RIR databaseAFRINIC 634 100% 67
2c0f:eb48:b000::/36 Valid RIR databaseAFRINIC 634 100% 67
2c0f:eb48:c000::/36 Valid RIR databaseAFRINIC 634 100% 67
2c0f:eb48:d000::/36 Valid RIR databaseAFRINIC 634 100% 67
2c0f:eb48:e000::/36 Valid RIR databaseAFRINIC 634 100% 67
2c0f:eb48:f000::/36 Valid RIR databaseAFRINIC 634 100% 67
2c0f:eb48:1000::/36 Valid RIR databaseAFRINIC 632 99% 67
2c0f:eb48:2000::/36 Valid RIR databaseAFRINIC 632 99% 67
2c0f:eb48:7000::/36 Valid RIR databaseAFRINIC 632 99% 67
102.22.242.0/23 Valid RIR databaseAFRINIC 195 29% 55
102.22.244.0/23 Valid RIR databaseAFRINIC 195 29% 55

AS-SET

PeeringDB's irr_as_set for AS328576: AFRINIC::AS-TELCOEXCHANGE. 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 (AS328576 isn't in the set, or no route object for AS328576 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 objectsAS328576 in itNot covered
AFRINIC::AS-TELCOEXCHANGE AFRINIC 73245 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 15 are in fix.csv.

  • Route object: not announced15

Route objects not announced

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

102.22.240.0/22AFRINICValid
102.22.240.0/23AFRINICValid
102.22.242.0/24AFRINICValid
102.22.244.0/22AFRINICValid
102.22.244.0/24AFRINICValid
102.22.246.0/23AFRINICValid
102.22.246.0/24AFRINICValid
102.218.156.0/23AFRINICValid
102.218.158.0/23AFRINICValid
102.219.60.0/23AFRINICValid
102.219.60.0/24AFRINICValid
102.219.62.0/23AFRINICValid
102.220.60.0/23AFRINICValid
102.221.200.0/23AFRINICValid
102.221.202.0/23AFRINICValid

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.