bgpreport

Network · data from 2026-11-12

AS23731 Tibra Global Services

Registry name: TGS-AS-AP - Tibra Global Services, AU · PeeringDB

4IPv4 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
0Low visibility seen by under 10% of full-table peers
56Route objects not announced registered with origin AS23731, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS23731, 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.
203.175.120.0/24 Valid RIR databaseAPNIC, RADB 671 100% 67
203.175.121.0/24 Valid RIR databaseAPNIC, RADB 671 100% 67
203.175.122.0/24 Valid RIR databaseAPNIC, RADB 671 100% 67
203.175.123.0/24 Valid RIR databaseAPNIC, RADB 671 100% 67

AS-SET

AS23731's PeeringDB record names no AS-SET.

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

  • Route object: not announced56

Route objects not announced

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

61.0.0.0/20REACHInvalid: origin
144.16.0.0/16REACHNo ROA
196.1.104.0/22REACHNo ROA
196.1.108.0/22REACHNo ROA
196.1.112.0/22REACHNo ROA
202.4.180.0/24REACHNo ROA
202.4.187.0/24REACHNo ROA
202.4.189.0/24REACHNo ROA
202.21.134.0/23REACHNo ROA
202.41.10.0/24REACHInvalid: origin
202.41.64.0/18REACHNo ROA
202.62.76.0/23REACHNo ROA
202.62.78.0/24REACHInvalid: origin
202.62.79.0/24REACHInvalid: origin
202.62.80.0/23REACHNo ROA
202.62.82.0/24REACHInvalid: origin
202.62.83.0/24REACHInvalid: origin
202.62.94.0/23REACHNo ROA
202.70.192.0/20REACHNo ROA
202.88.128.0/18REACHNo ROA
202.88.208.0/23REACHNo ROA
202.88.211.0/24REACHNo ROA
202.88.212.0/22REACHNo ROA
202.90.32.0/23REACHNo ROA
202.90.34.0/24REACHInvalid: origin
202.90.36.0/24REACHInvalid: origin
202.90.39.0/24REACHInvalid: origin
202.90.40.0/24REACHInvalid: origin
202.90.98.0/23REACHInvalid: origin
202.91.64.0/19REACHNo ROA
202.134.160.0/19REACHNo ROA
202.141.0.0/17REACHInvalid: origin
202.141.128.0/19REACHInvalid: origin
202.157.90.0/23REACHNo ROA
202.159.192.0/19REACHInvalid: origin
202.159.224.0/19REACHInvalid: origin
203.90.64.0/18REACHNo ROA
203.90.98.0/23REACHNo ROA
203.94.192.0/20REACHInvalid: origin
203.94.202.0/23REACHInvalid: origin
203.94.204.0/23REACHInvalid: origin
203.94.206.0/24REACHInvalid: origin
203.94.240.0/20REACHInvalid: origin
203.94.246.0/23REACHInvalid: origin
203.94.248.0/21REACHInvalid: origin
203.115.96.0/20REACHInvalid: origin
203.115.126.0/24REACHInvalid: origin
203.175.120.0/22NTTCOM, RADBNo ROA
203.195.152.0/22REACHInvalid: origin
203.195.176.0/21REACHInvalid: origin
203.195.214.0/23REACHInvalid: origin
203.195.231.0/24REACHInvalid: origin
210.18.128.0/19REACHNo ROA
210.18.130.0/23REACHNo ROA
210.212.0.0/16REACHInvalid: origin
218.248.0.0/16REACHNo 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.