bgpreport

Network · data from 2026-11-12

AS45413 SERVENET-AS-TH-AP - ServeNET Solution Limited Partnership

Registry name: SERVENET-AS-TH-AP - ServeNET Solution Limited Partnership, TH · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS45413, 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.
124.109.0.0/24 No ROA Other IRR onlyRADB 672 100% 68
124.109.1.0/24 No ROA Other IRR onlyRADB 672 100% 68
124.109.3.0/24 No ROA Other IRR onlyRADB 672 100% 68
2401:500::/36 No ROA Other IRR onlyRADB 5 1%low visibility 4
124.109.2.0/24 No ROA RIR databaseAPNIC, RADB 672 100% 68
14.128.9.0/24 No ROA RIR databaseAPNIC, RADB 671 100% 68
14.128.10.0/24 No ROA RIR databaseAPNIC, RADB 671 100% 68
14.128.11.0/24 No ROA RIR databaseAPNIC, RADB 671 100% 68

AS-SET

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

  • ROA: none8
  • Route object: RIR4
  • Route object: not announced6
ChangePrefix or setDetailFull-table peers
ROA: none124.109.0.0/24No ROA covers it. Add a ROA for AS45413, maxLength 24.672 of 673
Route object: RIR124.109.0.0/24Route object only in RADB. Add it in the RIR database for the space.672 of 673
ROA: none124.109.1.0/24No ROA covers it. Add a ROA for AS45413, maxLength 24.672 of 673
Route object: RIR124.109.1.0/24Route object only in RADB. Add it in the RIR database for the space.672 of 673
ROA: none124.109.3.0/24No ROA covers it. Add a ROA for AS45413, maxLength 24.672 of 673
Route object: RIR124.109.3.0/24Route object only in RADB. Add it in the RIR database for the space.672 of 673
ROA: none2401:500::/36No ROA covers it. Add a ROA for AS45413, maxLength 36.5 of 636
Route object: RIR2401:500::/36Route object only in RADB. Add it in the RIR database for the space.5 of 636
ROA: none124.109.2.0/24No ROA covers it. Add a ROA for AS45413, maxLength 24.672 of 673
ROA: none14.128.9.0/24No ROA covers it. Add a ROA for AS45413, maxLength 24.671 of 673
ROA: none14.128.10.0/24No ROA covers it. Add a ROA for AS45413, maxLength 24.671 of 673
ROA: none14.128.11.0/24No ROA covers it. Add a ROA for AS45413, maxLength 24.671 of 673

Route objects not announced

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

43.249.34.0/24RADBNo ROA
124.109.0.0/22RADBNo ROA
124.109.0.0/23RADBNo ROA
2401:500:2::/48APNICNo ROA
2401:500:1000::/36APNICNo ROA
2401:500:9000::/36RADBNo 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.