bgpreport

Network · data from 2026-11-12

AS23727 MANSOL-AS-AU - Managed Solutions Internet AS Internet Service Provider

Registry name: MANSOL-AS-AU - Managed Solutions Internet AS Internet Service Provider, AU · not in PeeringDB

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

Announced routes

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

192.189.148.0/24 No ROA Other origin only 651 97% 67
203.26.113.0/24 No ROA Other origin only 2 0%low visibility 2
202.94.32.0/20 Valid RIR databaseAPNIC 673 100% 67
203.24.63.0/24 Valid RIR databaseAPNIC 671 100% 67
203.27.44.0/24 Valid RIR databaseAPNIC 671 100% 67
203.55.134.0/23 Valid RIR databaseAPNIC 671 100% 67

AS-SET

AS23727 isn't in PeeringDB, where networks name their 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 8 are in fix.csv.

  • ROA: none2
  • Route object: none2
  • Route object: not announced4
ChangePrefix or setDetailFull-table peers
ROA: none192.189.148.0/24No ROA covers it. Add a ROA for AS23727, maxLength 24.651 of 673
Route object: none192.189.148.0/24Route objects for it name AS4851, AS7545, AS24130. Add a route object with origin AS23727 in the RIR database for the space.651 of 673
ROA: none203.26.113.0/24No ROA covers it. Add a ROA for AS23727, maxLength 24.2 of 673
Route object: none203.26.113.0/24Route objects for it name AS4851, AS7545, AS24130. Add a route object with origin AS23727 in the RIR database for the space.2 of 673

Route objects not announced

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

203.29.208.0/23APNIC, RADBValid
210.9.54.0/25RADBNo ROA
210.9.152.0/23RADBNo ROA
210.9.189.0/24RADBNo 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.