bgpreport

Network · data from 2026-11-12

AS136306 Texes Connect

Registry name: TEXES-AS - Texes Connect Private Limited, IN · PeeringDB

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

Announced routes

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

2403:5840::/32 No ROA RIR databaseAPNIC, RADB 635 100% 70
38.97.141.0/24 Valid Other IRR onlyRADB 672 100% 67
38.97.142.0/24 Valid Other IRR onlyRADB 672 100% 67
38.97.143.0/24 Valid Other IRR onlyRADB 672 100% 67
103.92.162.0/24 Valid RIR databaseAPNIC 673 100% 67
103.120.130.0/24 Valid RIR databaseAPNIC, RADB 673 100% 67
103.155.56.0/23 Valid RIR databaseAPNIC 673 100% 66
103.176.170.0/24 Valid RIR databaseAPNIC 673 100% 66
103.176.171.0/24 Valid RIR databaseAPNIC 673 100% 66
2001:df4:ba80::/48 Valid RIR databaseAPNIC 635 100% 70

AS-SET

PeeringDB's irr_as_set for AS136306: AS136306:AS-TEXES-BGP-PEERS. 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 (AS136306 isn't in the set, or no route object for AS136306 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 objectsAS136306 in itNot covered
AS136306:AS-TEXES-BGP-PEERS APNIC 8234 Yes 0

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

  • ROA: none1
  • Route object: RIR3
  • Route object: not announced6
ChangePrefix or setDetailFull-table peers
ROA: none2403:5840::/32No ROA covers it. Add a ROA for AS136306, maxLength 32.635 of 636
Route object: RIR38.97.141.0/24Route object only in RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR38.97.142.0/24Route object only in RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR38.97.143.0/24Route object only in RADB. Add it in the RIR database for the space.672 of 673

Route objects not announced

Route objects with origin AS136306 whose prefix no peer sees AS136306 announce. Many are kept on purpose (backup routes, space announced only in some places).

38.97.140.0/22ARINValid
38.97.140.0/24RADBValid
103.155.56.0/24APNICValid
103.155.57.0/24APNICValid
103.176.170.0/23APNICValid
2403:5840:2000::/48APNICValid

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.