bgpreport

Network · data from 2026-11-12

AS135060 Telair

Registry name: TELAIRPTYLTD-AS-AP - Telair Pty Ltd, AU · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS135060, 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.
2404:6a80:100::/41 Valid Nonecovered by 2404:6a80::/32 633 100% 67
103.93.150.0/24 Valid Other IRR onlyRADB 670 100% 67
111.235.140.0/22 Valid Other IRR onlyRADB 669 99% 67
103.126.146.0/24 Valid RIR databaseAPNIC, RADB 671 100% 67
103.208.5.0/24 Valid RIR databaseAPNIC, RADB 671 100% 67
116.206.129.0/24 Valid RIR databaseAPNIC 671 100% 67
123.100.145.0/24 Valid RIR databaseAPNIC, RADB 671 100% 67
123.100.146.0/24 Valid RIR databaseAPNIC 671 100% 67
123.100.148.0/24 Valid RIR databaseAPNIC, RADB 671 100% 67
123.100.150.0/24 Valid RIR databaseAPNIC, RADB 671 100% 67
123.100.152.0/24 Valid RIR databaseAPNIC, RADB 671 100% 67
103.43.178.0/24 Valid RIR databaseAPNIC 670 100% 67
103.43.179.0/24 Valid RIR databaseAPNIC 670 100% 67
103.126.145.0/24 Valid RIR databaseAPNIC, RADB 670 100% 67
103.126.147.0/24 Valid RIR databaseAPNIC, RADB 670 100% 67
103.152.129.0/24 Valid RIR databaseAPNIC 670 100% 67
103.208.7.0/24 Valid RIR databaseAPNIC, RADB 670 100% 67
123.100.141.0/24 Valid RIR databaseAPNIC 670 100% 67
123.100.143.0/24 Valid RIR databaseAPNIC 670 100% 67
123.100.147.0/24 Valid RIR databaseAPNIC, RADB 670 100% 67
123.100.149.0/24 Valid RIR databaseAPNIC, RADB 670 100% 67
123.100.151.0/24 Valid RIR databaseAPNIC 670 100% 67
123.253.193.0/24 Valid RIR databaseAPNIC 670 100% 67
202.86.53.0/24 Valid RIR databaseAPNIC 670 100% 67
202.86.55.0/24 Valid RIR databaseAPNIC 670 100% 67
203.34.177.0/24 Valid RIR databaseAPNIC 670 100% 67
103.93.151.0/24 Valid RIR databaseAPNIC, RADB 669 99% 67
103.126.144.0/24 Valid RIR databaseAPNIC, RADB 669 99% 67
103.152.128.0/24 Valid RIR databaseAPNIC, RADB 669 99% 67
103.208.4.0/24 Valid RIR databaseAPNIC, RADB 669 99% 67
103.208.6.0/24 Valid RIR databaseAPNIC, RADB 669 99% 67
111.235.140.0/24 Valid RIR databaseAPNIC, RADB 669 99% 67
111.235.141.0/24 Valid RIR databaseAPNIC, RADB 669 99% 67
111.235.142.0/24 Valid RIR databaseAPNIC, RADB 669 99% 67
111.235.143.0/24 Valid RIR databaseAPNIC, RADB 669 99% 67
116.206.128.0/24 Valid RIR databaseAPNIC, RADB 669 99% 67
123.100.140.0/24 Valid RIR databaseAPNIC 669 99% 67
123.100.144.0/24 Valid RIR databaseAPNIC 669 99% 67
123.253.192.0/24 Valid RIR databaseAPNIC 669 99% 67
123.253.194.0/24 Valid RIR databaseAPNIC 669 99% 67
125.254.60.0/24 Valid RIR databaseAPNIC, RADB 669 99% 67
125.254.61.0/24 Valid RIR databaseAPNIC, RADB 669 99% 67
202.86.52.0/24 Valid RIR databaseAPNIC 669 99% 67
202.86.54.0/24 Valid RIR databaseAPNIC 669 99% 67
2404:6a80::/41 Valid RIR databaseAPNIC 635 100% 67
2404:6a80:200::/41 Valid RIR databaseAPNIC 635 100% 67

AS-SET

PeeringDB's irr_as_set for AS135060: AS135060:AS-CONE. 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 (AS135060 isn't in the set, or no route object for AS135060 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 objectsAS135060 in itNot covered
AS135060:AS-CONE RADB 176210 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.

  • Route object: none1
  • Route object: RIR2
  • Route object: not announced7
ChangePrefix or setDetailFull-table peers
Route object: none2404:6a80:100::/41No route object for it. A route object for 2404:6a80::/32 with origin AS135060 covers it (filters allowing more-specifics accept it). Add a route object with origin AS135060 in the RIR database for the space.633 of 636
Route object: RIR103.93.150.0/24Route object only in RADB. Add it in the RIR database for the space.670 of 673
Route object: RIR111.235.140.0/22Route object only in RADB. Add it in the RIR database for the space.669 of 673

Route objects not announced

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

103.43.178.0/23APNICValid
103.126.144.0/22APNICValid
103.208.4.0/22APNIC, RADBValid
123.100.140.0/23APNICValid
123.100.148.0/22APNIC, RADBValid
2001:df5:df40::/48APNICValid
2404:6a80::/32RADBNo ROA

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.