bgpreport

Network · data from 2026-11-12

AS55688 Jagoan Hosting

Registry name: BEON-AS-ID - PT. Beon Intermedia, ID · PeeringDB

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

Announced routes

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

38.9.44.0/24 No ROA Other IRR onlyRADB 673 100% 69
38.9.45.0/24 No ROA Other IRR onlyRADB 673 100% 69
38.9.46.0/24 No ROA Other IRR onlyRADB 673 100% 69
38.9.47.0/24 No ROA Other IRR onlyRADB 673 100% 68
38.103.170.0/24 No ROA Other IRR onlyRADB 673 100% 69
38.103.171.0/24 No ROA Other IRR onlyRADB 673 100% 69
38.147.122.0/24 No ROA Other IRR onlyRADB 673 100% 70
154.19.37.0/24 No ROA Other IRR onlyRADB 673 100% 69
38.68.69.0/24 No ROA RIR databaseARIN, RADB 673 100% 69
101.50.0.0/24 Valid Other IRR onlyRADB 673 100% 69
101.50.1.0/24 Valid Other IRR onlyRADB 673 100% 66
103.16.117.0/24 Valid Other IRR onlyRADB 673 100% 69
103.27.207.0/24 Valid Other IRR onlyNTTCOM, RADB 673 100% 69
103.56.148.0/24 Valid Other IRR onlyNTTCOM, RADB 673 100% 70
103.56.149.0/24 Valid Other IRR onlyNTTCOM, RADB 673 100% 69
103.163.138.0/24 Valid Other IRR onlyRADB 673 100% 70
103.163.139.0/24 Valid Other IRR onlyRADB 673 100% 69
103.245.38.0/24 Valid Other IRR onlyRADB 673 100% 69
157.66.34.0/24 Valid Other IRR onlyRADB 673 100% 69
157.66.35.0/24 Valid Other IRR onlyRADB 673 100% 70
101.50.2.0/24 Valid Other IRR onlyNTTCOM, RADB 672 100% 70
103.16.116.0/24 Valid Other IRR onlyRADB 672 100% 69
103.27.206.0/24 Valid Other IRR onlyNTTCOM, RADB 672 100% 69
103.245.39.0/24 Valid Other IRR onlyRADB 672 100% 70
101.50.3.0/24 Valid Other IRR onlyRADB 670 100% 69
103.157.97.0/24 Valid RIR databaseAPNIC, RADB 673 100% 69
103.166.156.0/24 Valid RIR databaseAPNIC, RADB 673 100% 69
103.166.157.0/24 Valid RIR databaseAPNIC, RADB 673 100% 69
103.157.96.0/24 Valid RIR databaseAPNIC, RADB 672 100% 69
2001:df4:3b00::/48 Valid RIR databaseAPNIC, RADB 635 100% 69
2406:a040:ff01::/48 Valid RIR databaseAPNIC, RADB 635 100% 69

AS-SET

PeeringDB's irr_as_set for AS55688: AS-BEON-ID. 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 (AS55688 isn't in the set, or no route object for AS55688 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 objectsAS55688 in itNot covered
AS-BEON-ID In no IRR database read today.

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

  • ROA: none9
  • Route object: RIR24
  • AS-SET: not found1
  • Route object: not announced15
ChangePrefix or setDetailFull-table peers
ROA: none38.9.44.0/24No ROA covers it. Add a ROA for AS55688, maxLength 24.673 of 673
Route object: RIR38.9.44.0/24Route object only in RADB. Add it in the RIR database for the space.673 of 673
ROA: none38.9.45.0/24No ROA covers it. Add a ROA for AS55688, maxLength 24.673 of 673
Route object: RIR38.9.45.0/24Route object only in RADB. Add it in the RIR database for the space.673 of 673
ROA: none38.9.46.0/24No ROA covers it. Add a ROA for AS55688, maxLength 24.673 of 673
Route object: RIR38.9.46.0/24Route object only in RADB. Add it in the RIR database for the space.673 of 673
ROA: none38.9.47.0/24No ROA covers it. Add a ROA for AS55688, maxLength 24.673 of 673
Route object: RIR38.9.47.0/24Route object only in RADB. Add it in the RIR database for the space.673 of 673
ROA: none38.103.170.0/24No ROA covers it. Add a ROA for AS55688, maxLength 24.673 of 673
Route object: RIR38.103.170.0/24Route object only in RADB. Add it in the RIR database for the space.673 of 673
ROA: none38.103.171.0/24No ROA covers it. Add a ROA for AS55688, maxLength 24.673 of 673
Route object: RIR38.103.171.0/24Route object only in RADB. Add it in the RIR database for the space.673 of 673
ROA: none38.147.122.0/24No ROA covers it. Add a ROA for AS55688, maxLength 24.673 of 673
Route object: RIR38.147.122.0/24Route object only in RADB. Add it in the RIR database for the space.673 of 673
ROA: none154.19.37.0/24No ROA covers it. Add a ROA for AS55688, maxLength 24.673 of 673
Route object: RIR154.19.37.0/24Route object only in RADB. Add it in the RIR database for the space.673 of 673
ROA: none38.68.69.0/24No ROA covers it. Add a ROA for AS55688, maxLength 24.673 of 673
Route object: RIR101.50.0.0/24Route object only in RADB. Add it in the RIR database for the space.673 of 673
Route object: RIR101.50.1.0/24Route object only in RADB. Add it in the RIR database for the space.673 of 673
Route object: RIR103.16.117.0/24Route object only in RADB. Add it in the RIR database for the space.673 of 673
Route object: RIR103.27.207.0/24Route object only in NTTCOM, RADB. Add it in the RIR database for the space.673 of 673
Route object: RIR103.56.148.0/24Route object only in NTTCOM, RADB. Add it in the RIR database for the space.673 of 673
Route object: RIR103.56.149.0/24Route object only in NTTCOM, RADB. Add it in the RIR database for the space.673 of 673
Route object: RIR103.163.138.0/24Route object only in RADB. Add it in the RIR database for the space.673 of 673
Route object: RIR103.163.139.0/24Route object only in RADB. Add it in the RIR database for the space.673 of 673
Route object: RIR103.245.38.0/24Route object only in RADB. Add it in the RIR database for the space.673 of 673
Route object: RIR157.66.34.0/24Route object only in RADB. Add it in the RIR database for the space.673 of 673
Route object: RIR157.66.35.0/24Route object only in RADB. Add it in the RIR database for the space.673 of 673
Route object: RIR101.50.2.0/24Route object only in NTTCOM, RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR103.16.116.0/24Route object only in RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR103.27.206.0/24Route object only in NTTCOM, RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR103.245.39.0/24Route object only in RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR101.50.3.0/24Route object only in RADB. Add it in the RIR database for the space.670 of 673
AS-SET: not foundAS-BEON-IDPeeringDB names AS-BEON-ID; no IRR database read has it.

Route objects not announced

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

38.9.44.0/22RADBNo ROA
38.103.170.0/23RADBNo ROA
101.50.0.0/22APNIC, NTTCOM, RADBValid
101.50.0.0/23RADBValid
101.50.2.0/23RADBValid
103.16.116.0/23RADBValid
103.27.206.0/23APNIC, NTTCOM, RADBValid
103.56.148.0/23APNIC, NTTCOM, RADBValid
103.157.96.0/23RADBValid
103.163.138.0/23RADBValid
103.166.156.0/23APNIC, RADBValid
103.245.38.0/23RADBValid
157.66.34.0/23RADBValid
2001:df2:ed40::/48RADBValid
2001:df3:d440::/48RADBNo 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.