bgpreport

Network · data from 2026-11-12

AS134862 Ultimate Internet Services

Registry name: ULTIMATE-AS-IN - Ultimate Internet Services Private Limited, IN · PeeringDB

7IPv4 routes 71.4% RPKI valid · 100.0% with a route object
1IPv6 routes 0.0% RPKI valid · 100.0% with a route object
2RPKI invalid 0 origin · 2 maxLength
1No 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 AS134862, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS134862, 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.
103.207.12.0/23 Invalid: maxLength RIR databaseAPNIC 142 21% 51
103.207.14.0/23 Invalid: maxLength RIR databaseAPNIC 142 21% 51
2001:df0:c780::/48 No ROA RIR databaseAPNIC 636 100% 70
103.207.12.0/22 Valid RIR databaseAPNIC 673 100% 66
103.207.12.0/24 Valid RIR databaseAPNIC 673 100% 66
103.207.13.0/24 Valid RIR databaseAPNIC 673 100% 66
103.207.14.0/24 Valid RIR databaseAPNIC 673 100% 66
103.207.15.0/24 Valid RIR databaseAPNIC 673 100% 66

AS-SET

PeeringDB's irr_as_set for AS134862: AS134862:AS-ULTIMATE. 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 (AS134862 isn't in the set, or no route object for AS134862 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 objectsAS134862 in itNot covered
AS134862:AS-ULTIMATE In no IRR database read today.

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

  • ROA: maxLength2
  • ROA: none1
  • AS-SET: not found1
ChangePrefix or setDetailFull-table peers
ROA: maxLength103.207.12.0/23ROA 103.207.12.0/22 AS134862 has maxLength 22; the route is a /23. Raise the maxLength, or add a ROA for 103.207.12.0/23.142 of 673
ROA: maxLength103.207.14.0/23ROA 103.207.12.0/22 AS134862 has maxLength 22; the route is a /23. Raise the maxLength, or add a ROA for 103.207.14.0/23.142 of 673
ROA: none2001:df0:c780::/48No ROA covers it. Add a ROA for AS134862, maxLength 48.636 of 636
AS-SET: not foundAS134862:AS-ULTIMATEPeeringDB names AS134862:AS-ULTIMATE; no IRR database read has it.

Route objects not announced

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