bgpreport

Network · data from 2026-11-12

AS201179 Teraline Telecom

Registry name: TERALINETELECOM-AS Teraline Telecom LLP, KZ · PeeringDB

10IPv4 routes 50.0% RPKI valid · 100.0% with a route object
1IPv6 routes 100.0% RPKI valid · 100.0% with a route object
0RPKI invalid 0 origin · 0 maxLength
5No 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 AS201179, seen from no peer

Announced routes

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

46.8.149.0/24 No ROA RIR databaseRIPE 673 100% 66
46.8.151.0/24 No ROA RIR databaseRIPE 673 100% 66
109.248.131.0/24 No ROA RIR databaseRIPE 673 100% 66
188.130.130.0/24 No ROA RIR databaseRIPE 673 100% 66
188.130.173.0/24 No ROA RIR databaseRIPE 673 100% 66
176.110.124.0/24 Valid RIR databaseRIPE 673 100% 66
176.110.125.0/24 Valid RIR databaseRIPE 673 100% 66
176.110.126.0/24 Valid RIR databaseRIPE 673 100% 66
185.18.220.0/24 Valid RIR databaseRIPE 673 100% 66
188.130.223.0/24 Valid RIR databaseRIPE 673 100% 66
2a13:1240::/29 Valid RIR databaseRIPE 634 100% 68

AS-SET

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

  • ROA: none5
ChangePrefix or setDetailFull-table peers
ROA: none46.8.149.0/24No ROA covers it. Add a ROA for AS201179, maxLength 24.673 of 673
ROA: none46.8.151.0/24No ROA covers it. Add a ROA for AS201179, maxLength 24.673 of 673
ROA: none109.248.131.0/24No ROA covers it. Add a ROA for AS201179, maxLength 24.673 of 673
ROA: none188.130.130.0/24No ROA covers it. Add a ROA for AS201179, maxLength 24.673 of 673
ROA: none188.130.173.0/24No ROA covers it. Add a ROA for AS201179, maxLength 24.673 of 673

Route objects not announced

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