bgpreport

Network · data from 2026-11-12

AS133315 Utopia Networks

Registry name: TERRAFIBR-AS - TERRAFIBER NETWORKS PRIVATE LIMITED, IN · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS133315, 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.
43.250.132.0/22 Valid RIR databaseAPNIC 672 100% 67
43.250.134.0/24 Valid RIR databaseAPNIC 672 100% 67
43.250.135.0/24 Valid RIR databaseAPNIC 672 100% 67
43.250.208.0/22 Valid RIR databaseAPNIC 672 100% 67
43.250.211.0/24 Valid RIR databaseAPNIC 672 100% 67
103.78.168.0/23 Valid RIR databaseAPNIC 672 100% 67
103.81.250.0/23 Valid RIR databaseAPNIC 672 100% 67
103.169.76.0/23 Valid RIR databaseAPNIC 672 100% 67
103.232.8.0/22 Valid RIR databaseAPNIC 672 100% 67
103.232.11.0/24 Valid RIR databaseAPNIC 672 100% 67
103.235.120.0/22 Valid RIR databaseAPNIC 672 100% 67
103.166.95.0/24 Valid RIR databaseAPNIC 671 100% 67
103.171.43.0/24 Valid RIR databaseAPNIC 671 100% 67
43.250.132.0/23 Valid RIR databaseAPNIC 42 6%low visibility 29
43.250.132.0/24 Valid RIR databaseAPNIC 42 6%low visibility 29
43.250.133.0/24 Valid RIR databaseAPNIC 42 6%low visibility 29
43.250.134.0/23 Valid RIR databaseAPNIC 42 6%low visibility 29
43.250.208.0/23 Valid RIR databaseAPNIC 42 6%low visibility 29
43.250.208.0/24 Valid RIR databaseAPNIC 42 6%low visibility 29
43.250.209.0/24 Valid RIR databaseAPNIC 42 6%low visibility 29
43.250.210.0/23 Valid RIR databaseAPNIC 42 6%low visibility 29
43.250.210.0/24 Valid RIR databaseAPNIC 42 6%low visibility 29
103.78.168.0/24 Valid RIR databaseAPNIC 42 6%low visibility 29
103.78.169.0/24 Valid RIR databaseAPNIC 42 6%low visibility 29
103.81.250.0/24 Valid RIR databaseAPNIC 42 6%low visibility 29
103.81.251.0/24 Valid RIR databaseAPNIC 42 6%low visibility 29
103.169.76.0/24 Valid RIR databaseAPNIC 42 6%low visibility 29
103.169.77.0/24 Valid RIR databaseAPNIC 42 6%low visibility 29
103.232.8.0/23 Valid RIR databaseAPNIC 42 6%low visibility 29
103.232.8.0/24 Valid RIR databaseAPNIC 42 6%low visibility 29
103.232.9.0/24 Valid RIR databaseAPNIC 42 6%low visibility 29
103.232.10.0/23 Valid RIR databaseAPNIC 42 6%low visibility 29
103.232.10.0/24 Valid RIR databaseAPNIC 42 6%low visibility 29
103.235.120.0/23 Valid RIR databaseAPNIC 42 6%low visibility 29
103.235.120.0/24 Valid RIR databaseAPNIC 42 6%low visibility 29
103.235.121.0/24 Valid RIR databaseAPNIC 42 6%low visibility 29
103.235.122.0/23 Valid RIR databaseAPNIC 42 6%low visibility 29
103.235.122.0/24 Valid RIR databaseAPNIC 42 6%low visibility 29
103.235.123.0/24 Valid RIR databaseAPNIC 42 6%low visibility 29

AS-SET

PeeringDB's irr_as_set for AS133315: AS133315:AS-CUSTOMERS. 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 (AS133315 isn't in the set, or no route object for AS133315 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 objectsAS133315 in itNot covered
AS133315:AS-CUSTOMERS APNIC 114142 Yes 0

Fix list

Nothing to change: every route is RPKI valid with a route object in an RIR database, and every route object is announced.

Route objects not announced

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