Network · data from 2026-11-12
AS134026 UltraNet Services
Registry name: ULTRANET-AS - Ultranet services private limited, IN · PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS134026, 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.
| 2405:80c0:2000::/48 | Invalid: maxLength | Nonecovered by 2405:80c0::/32 | 1 0%low visibility |
| 2405:80c0:2001::/48 | Invalid: maxLength | Nonecovered by 2405:80c0::/32 | 1 0%low visibility |
| 103.179.223.0/24 | No ROA | Other origin only | 672 100% |
| 2407:c8c0::/32 | No ROA | None | 636 100% |
| 2001:df2:d00::/48 | No ROA | RIR databaseAPNIC | 636 100% |
| 45.115.104.0/22 | Valid | RIR databaseAPNIC | 672 100% |
| 45.115.104.0/23 | Valid | RIR databaseAPNIC | 672 100% |
| 45.115.106.0/23 | Valid | RIR databaseAPNIC | 672 100% |
| 103.55.88.0/22 | Valid | RIR databaseAPNIC | 672 100% |
| 103.55.88.0/23 | Valid | RIR databaseAPNIC | 672 100% |
| 103.55.90.0/23 | Valid | RIR databaseAPNIC | 672 100% |
| 103.70.200.0/22 | Valid | RIR databaseAPNIC | 672 100% |
| 103.70.200.0/23 | Valid | RIR databaseAPNIC | 672 100% |
| 103.70.202.0/23 | Valid | RIR databaseAPNIC | 672 100% |
| 103.131.27.0/24 | Valid | RIR databaseAPNIC | 672 100% |
| 103.140.219.0/24 | Valid | RIR databaseAPNIC | 672 100% |
| 103.184.70.0/23 | Valid | RIR databaseAPNIC | 671 100% |
| 2405:80c0::/32 | Valid | RIR databaseAPNIC | 636 100% |
| 45.115.104.0/24 | Valid | RIR databaseAPNIC | 39 6%low visibility |
| 45.115.105.0/24 | Valid | RIR databaseAPNIC | 39 6%low visibility |
| 45.115.106.0/24 | Valid | RIR databaseAPNIC | 39 6%low visibility |
| 45.115.107.0/24 | Valid | RIR databaseAPNIC | 39 6%low visibility |
| 103.55.88.0/24 | Valid | RIR databaseAPNIC | 39 6%low visibility |
| 103.55.89.0/24 | Valid | RIR databaseAPNIC | 39 6%low visibility |
| 103.55.90.0/24 | Valid | RIR databaseAPNIC | 39 6%low visibility |
| 103.55.91.0/24 | Valid | RIR databaseAPNIC | 39 6%low visibility |
| 103.70.200.0/24 | Valid | RIR databaseAPNIC | 39 6%low visibility |
| 103.70.201.0/24 | Valid | RIR databaseAPNIC | 39 6%low visibility |
| 103.70.202.0/24 | Valid | RIR databaseAPNIC | 39 6%low visibility |
| 103.70.203.0/24 | Valid | RIR databaseAPNIC | 39 6%low visibility |
| 103.184.70.0/24 | Valid | RIR databaseAPNIC | 39 6%low visibility |
| 103.184.71.0/24 | Valid | RIR databaseAPNIC | 39 6%low visibility |
AS-SET
PeeringDB's irr_as_set for AS134026: AS134026:AS-ULTRANET. 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 (AS134026 isn't in the set, or no route object for AS134026 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.
| Name | Database | ASNs | Sets | AS134026 in it | Not covered |
|---|---|---|---|---|---|
| AS134026:AS-ULTRANET | APNIClists itself further down5 member sets in no database: AS-6186, AS-HNSISP-TRANSIT, AS136346:AS-FASTTNET, AS137609:AS-DCSISPL, AS214174:AS-RIPE | 716 | 74 | Yes | 2 |
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 18 are in fix.csv.
- ROA: maxLength2
- ROA: none3
- Route object: none4
- AS-SET: missing member5
- Route object: not announced4
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: maxLength | 2405:80c0:2000::/48 | ROA 2405:80c0::/32 AS134026 has maxLength 32; the route is a /48. Raise the maxLength, or add a ROA for 2405:80c0:2000::/48. |
| Route object: none | 2405:80c0:2000::/48 | No route object for it. A route object for 2405:80c0::/32 with origin AS134026 covers it (filters allowing more-specifics accept it). Add a route object with origin AS134026 in the RIR database for the space. |
| ROA: maxLength | 2405:80c0:2001::/48 | ROA 2405:80c0::/32 AS134026 has maxLength 32; the route is a /48. Raise the maxLength, or add a ROA for 2405:80c0:2001::/48. |
| Route object: none | 2405:80c0:2001::/48 | No route object for it. A route object for 2405:80c0::/32 with origin AS134026 covers it (filters allowing more-specifics accept it). Add a route object with origin AS134026 in the RIR database for the space. |
| ROA: none | 103.179.223.0/24 | No ROA covers it. Add a ROA for AS134026, maxLength 24. |
| Route object: none | 103.179.223.0/24 | Route objects for it name AS17665. Add a route object with origin AS134026 in the RIR database for the space. |
| ROA: none | 2407:c8c0::/32 | No ROA covers it. Add a ROA for AS134026, maxLength 32. |
| Route object: none | 2407:c8c0::/32 | No route object for it. Add a route object with origin AS134026 in the RIR database for the space. |
| ROA: none | 2001:df2:d00::/48 | No ROA covers it. Add a ROA for AS134026, maxLength 48. |
| AS-SET: missing member | AS134026:AS-ULTRANET | AS134026:AS-ULTRANET (APNIC) lists AS-6186; no IRR database read has it. |
| AS-SET: missing member | AS134026:AS-ULTRANET | AS134026:AS-ULTRANET (APNIC) lists AS-HNSISP-TRANSIT; no IRR database read has it. |
| AS-SET: missing member | AS134026:AS-ULTRANET | AS134026:AS-ULTRANET (APNIC) lists AS136346:AS-FASTTNET; no IRR database read has it. |
| AS-SET: missing member | AS134026:AS-ULTRANET | AS134026:AS-ULTRANET (APNIC) lists AS137609:AS-DCSISPL; no IRR database read has it. |
| AS-SET: missing member | AS134026:AS-ULTRANET | AS134026:AS-ULTRANET (APNIC) lists AS214174:AS-RIPE; no IRR database read has it. |
Route objects not announced
Route objects with origin AS134026 whose prefix no peer sees AS134026 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 43.229.161.0/24 | RADB | No ROA |
| 103.92.112.0/24 | APNIC | Valid |
| 103.177.174.0/24 | APNIC | Valid |
| 2405:5c0::/32 | APNIC | Valid |
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.