bgpreport

Network · data from 2026-11-12

AS35830 BTTGROUP-AS Fast Servers (Pty) Ltd

Registry name: BTTGROUP-AS Fast Servers (Pty) Ltd, ZA · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS35830, 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.
45.66.209.0/24 No ROA RIR databaseRIPE 669 99% 68
45.159.20.0/24 No ROA RIR databaseRIPE 669 99% 68
5.181.171.0/24 Valid RIR databaseRIPE 669 99% 68
5.183.254.0/24 Valid RIR databaseRIPE 669 99% 68
45.66.210.0/24 Valid RIR databaseRIPE 669 99% 68
45.66.211.0/24 Valid RIR databaseRIPE 669 99% 68
45.80.106.0/23 Valid RIR databaseRIPE 669 99% 68
45.88.13.0/24 Valid RIR databaseRIPE 669 99% 68
45.132.186.0/24 Valid RIR databaseRIPE 669 99% 68
45.132.187.0/24 Valid RIR databaseRIPE 669 99% 68
45.148.126.0/24 Valid RIR databaseRIPE 669 99% 68
62.3.0.0/24 Valid RIR databaseRIPE 669 99% 68
77.81.65.0/24 Valid RIR databaseRIPE 669 99% 68
89.19.35.0/24 Valid RIR databaseRIPE 669 99% 68
89.47.55.0/24 Valid RIR databaseRIPE 669 99% 68
130.49.76.0/24 Valid RIR databaseRIPE 669 99% 68
130.49.77.0/24 Valid RIR databaseRIPE 669 99% 68
130.49.78.0/24 Valid RIR databaseRIPE 669 99% 68
130.49.79.0/24 Valid RIR databaseRIPE 669 99% 68
130.49.112.0/24 Valid RIR databaseRIPE 669 99% 68
130.49.113.0/24 Valid RIR databaseRIPE 669 99% 68
130.49.114.0/24 Valid RIR databaseRIPE 669 99% 68
130.49.115.0/24 Valid RIR databaseRIPE 669 99% 68
166.1.131.0/24 Valid RIR databaseARIN 669 99% 68
185.61.216.0/24 Valid RIR databaseRIPE 669 99% 68
185.61.220.0/24 Valid RIR databaseRIPE 669 99% 68
185.81.144.0/24 Valid RIR databaseRIPE 669 99% 68
185.81.145.0/24 Valid RIR databaseRIPE 669 99% 68
185.88.102.0/24 Valid RIR databaseRIPE 669 99% 68
185.88.103.0/24 Valid RIR databaseRIPE 669 99% 68
185.96.37.0/24 Valid RIR databaseRIPE 669 99% 68
185.102.112.0/24 Valid RIR databaseRIPE 669 99% 68
185.102.113.0/24 Valid RIR databaseRIPE 669 99% 68
193.151.188.0/24 Valid RIR databaseRIPE 669 99% 68
212.119.40.0/23 Valid RIR databaseRIPE 669 99% 68
213.232.121.0/24 Valid RIR databaseRIPE 669 99% 68
213.232.123.0/24 Valid RIR databaseRIPE 669 99% 68

AS-SET

AS35830 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 2 are in fix.csv.

  • ROA: none2
ChangePrefix or setDetailFull-table peers
ROA: none45.66.209.0/24No ROA covers it. Add a ROA for AS35830, maxLength 24.669 of 673
ROA: none45.159.20.0/24No ROA covers it. Add a ROA for AS35830, maxLength 24.669 of 673

Route objects not announced

Every route object with origin AS35830 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.