bgpreport

Network · data from 2026-11-12

AS55707 Simtronic Technologies

Registry name: SIMTRONIC-AS-AP - Simtronic, AU · PeeringDB

31IPv4 routes 96.8% RPKI valid · 100.0% with a route object
0IPv6 routes
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
72Route objects not announced registered with origin AS55707, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS55707, 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.23.104.0/22 No ROA Other IRR onlyRADB 672 100% 66
101.2.168.0/24 Valid RIR databaseAPNIC 672 100% 66
101.2.169.0/24 Valid RIR databaseAPNIC 672 100% 66
101.2.170.0/24 Valid RIR databaseAPNIC 672 100% 66
101.2.171.0/24 Valid RIR databaseAPNIC 672 100% 66
103.1.108.0/24 Valid RIR databaseAPNIC, RADB 672 100% 66
103.1.109.0/24 Valid RIR databaseAPNIC, RADB 672 100% 66
103.7.72.0/24 Valid RIR databaseAPNIC 672 100% 66
103.7.73.0/24 Valid RIR databaseAPNIC 672 100% 66
103.7.74.0/24 Valid RIR databaseAPNIC 672 100% 66
103.7.75.0/24 Valid RIR databaseAPNIC 672 100% 66
103.23.104.0/23 Valid RIR databaseAPNIC 672 100% 66
103.23.104.0/24 Valid RIR databaseAPNIC, RADB 672 100% 66
103.23.105.0/24 Valid RIR databaseAPNIC 672 100% 66
103.23.106.0/23 Valid RIR databaseAPNIC 672 100% 66
119.63.200.0/21 Valid RIR databaseAPNIC, RADB 672 100% 66
163.47.252.0/22 Valid RIR databaseAPNIC, NTTCOM 672 100% 66
163.47.252.0/24 Valid RIR databaseAPNIC 672 100% 66
163.47.253.0/24 Valid RIR databaseAPNIC 672 100% 66
163.47.254.0/24 Valid RIR databaseAPNIC 672 100% 66
163.47.255.0/24 Valid RIR databaseAPNIC 672 100% 66
202.45.152.0/22 Valid RIR databaseAPNIC, RADB 672 100% 66
203.31.114.0/23 Valid RIR databaseAPNIC 672 100% 66
203.31.114.0/24 Valid RIR databaseAPNIC, NTTCOM 672 100% 66
203.31.115.0/24 Valid RIR databaseAPNIC, NTTCOM 672 100% 66
223.25.112.0/21 Valid RIR databaseAPNIC 672 100% 66
223.25.112.0/24 Valid RIR databaseAPNIC, RADB 672 100% 66
223.25.114.0/24 Valid RIR databaseAPNIC 672 100% 66
223.25.115.0/24 Valid RIR databaseAPNIC 672 100% 66
103.23.106.0/24 Valid RIR databaseAPNIC 670 100% 66
103.23.107.0/24 Valid RIR databaseAPNIC 670 100% 66

AS-SET

AS55707'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 74 are in fix.csv.

  • ROA: none1
  • Route object: RIR1
  • Route object: not announced72
ChangePrefix or setDetailFull-table peers
ROA: none103.23.104.0/22No ROA covers it. Add a ROA for AS55707, maxLength 22.672 of 673
Route object: RIR103.23.104.0/22Route object only in RADB. Add it in the RIR database for the space.672 of 673

Route objects not announced

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

43.243.20.0/24NTTCOM, RADBNo ROA
44.136.158.0/24NTTCOMNo ROA
44.136.159.0/24NTTCOMNo ROA
44.136.201.0/24NTTCOMNo ROA
44.136.224.0/24NTTCOMNo ROA
44.136.227.0/24NTTCOMNo ROA
45.122.231.0/24RADBNo ROA
45.124.110.0/23RADBNo ROA
101.2.168.0/22APNIC, RADBValid
101.2.168.0/23APNIC, NTTCOMValid
101.2.170.0/23APNIC, NTTCOMValid
103.1.108.0/22APNIC, NTTCOMValid
103.1.108.0/23APNIC, NTTCOMValid
103.1.110.0/23APNIC, NTTCOMValid
103.1.110.0/24APNIC, RADBValid
103.1.111.0/24APNICValid
103.5.76.0/23RADBNo ROA
103.5.76.0/24NTTCOMNo ROA
103.5.77.0/24NTTCOMNo ROA
103.7.72.0/22APNIC, RADBValid
103.7.72.0/23APNIC, NTTCOMValid
103.7.74.0/23APNIC, NTTCOMValid
103.38.145.0/24NTTCOM, RADBNo ROA
103.38.148.0/23NTTCOM, RADBNo ROA
103.38.148.0/24NTTCOMNo ROA
103.38.149.0/24NTTCOMNo ROA
103.61.69.0/24RADBNo ROA
103.100.196.0/22RADBNo ROA
103.224.162.0/24NTTCOM, RADBNo ROA
103.232.170.0/23RADBNo ROA
119.63.200.0/22APNICValid
119.63.200.0/23APNICValid
119.63.200.0/24APNICValid
119.63.201.0/24APNICValid
119.63.202.0/23APNICValid
119.63.202.0/24APNICValid
119.63.203.0/24APNICValid
119.63.204.0/22APNICValid
119.63.204.0/23APNICValid
119.63.204.0/24APNICValid
119.63.205.0/24APNICValid
119.63.206.0/23APNICValid
119.63.206.0/24APNICValid
119.63.207.0/24APNICValid
163.47.216.0/22RADBNo ROA
163.47.252.0/23APNICValid
163.47.254.0/23APNICValid
202.45.152.0/23APNICValid
202.45.152.0/24APNICValid
202.45.153.0/24APNICValid
202.45.154.0/23APNICValid
202.45.154.0/24APNICValid
202.45.155.0/24APNICValid
202.52.129.0/24NTTCOMNo ROA
203.24.120.0/24NTTCOMNo ROA
203.26.188.0/23NTTCOMNo ROA
203.31.7.0/24RADBNo ROA
203.56.37.0/24NTTCOMNo ROA
203.88.104.0/22RADBNo ROA
223.25.112.0/22APNIC, NTTCOMValid
223.25.112.0/23APNIC, NTTCOMValid
223.25.113.0/24APNIC, RADBValid
223.25.114.0/23APNIC, NTTCOMValid
223.25.116.0/22APNIC, NTTCOMValid
223.25.116.0/23APNIC, NTTCOMValid
223.25.116.0/24APNICValid
223.25.117.0/24APNIC, RADBValid
223.25.118.0/23APNIC, NTTCOMValid
223.25.118.0/24APNICValid
223.25.119.0/24APNICValid
2401:2bc0::/32RADBNo ROA
2406:8a00::/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.