bgpreport

Network · data from 2026-11-12

AS55514 Electricity Generating Authority of Thailand (EGAT)

Registry name: EGAT-CO-TH - Electricity Generating Authority of Thailand (EGAT), TH · PeeringDB

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

Announced routes

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

182.255.11.0/24 No ROA Other origin onlycovered by 182.255.8.0/22 673 100% 69
182.255.15.0/24 No ROA Other origin only 673 100% 69
182.255.12.0/24 No ROA Other origin onlycovered by 182.255.12.0/23 672 100% 69
182.255.13.0/24 No ROA Other origin onlycovered by 182.255.12.0/23 672 100% 69
182.255.14.0/24 No ROA Other origin only 672 100% 69
182.255.8.0/21 No ROA Other origin only 671 100% 69
182.255.8.0/24 No ROA Other IRR onlyNTTCOM 672 100% 69
182.255.9.0/24 No ROA Other IRR onlyNTTCOM 672 100% 69
182.255.10.0/24 No ROA Other IRR onlyNTTCOM 672 100% 69
171.102.39.0/24 Valid RIR databaseAPNIC, RADB 670 100% 68

AS-SET

AS55514'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 22 are in fix.csv.

  • ROA: none9
  • Route object: none6
  • Route object: RIR3
  • Route object: not announced4
ChangePrefix or setDetailFull-table peers
ROA: none182.255.11.0/24No ROA covers it. Add a ROA for AS55514, maxLength 24.673 of 673
Route object: none182.255.11.0/24Route objects for it name AS9304, AS38082. A route object for 182.255.8.0/22 with origin AS55514 covers it (filters allowing more-specifics accept it). Add a route object with origin AS55514 in the RIR database for the space.673 of 673
ROA: none182.255.15.0/24No ROA covers it. Add a ROA for AS55514, maxLength 24.673 of 673
Route object: none182.255.15.0/24Route objects for it name AS9304, AS38082. Add a route object with origin AS55514 in the RIR database for the space.673 of 673
ROA: none182.255.12.0/24No ROA covers it. Add a ROA for AS55514, maxLength 24.672 of 673
Route object: none182.255.12.0/24Route objects for it name AS9304, AS38082. A route object for 182.255.12.0/23 with origin AS55514 covers it (filters allowing more-specifics accept it). Add a route object with origin AS55514 in the RIR database for the space.672 of 673
ROA: none182.255.13.0/24No ROA covers it. Add a ROA for AS55514, maxLength 24.672 of 673
Route object: none182.255.13.0/24Route objects for it name AS9304, AS38082. A route object for 182.255.12.0/23 with origin AS55514 covers it (filters allowing more-specifics accept it). Add a route object with origin AS55514 in the RIR database for the space.672 of 673
ROA: none182.255.14.0/24No ROA covers it. Add a ROA for AS55514, maxLength 24.672 of 673
Route object: none182.255.14.0/24Route objects for it name AS9304, AS38082. Add a route object with origin AS55514 in the RIR database for the space.672 of 673
ROA: none182.255.8.0/21No ROA covers it. Add a ROA for AS55514, maxLength 21.671 of 673
Route object: none182.255.8.0/21Route objects for it name AS9304, AS38082, AS45629. Add a route object with origin AS55514 in the RIR database for the space.671 of 673
ROA: none182.255.8.0/24No ROA covers it. Add a ROA for AS55514, maxLength 24.672 of 673
Route object: RIR182.255.8.0/24Route object only in NTTCOM. Add it in the RIR database for the space.672 of 673
ROA: none182.255.9.0/24No ROA covers it. Add a ROA for AS55514, maxLength 24.672 of 673
Route object: RIR182.255.9.0/24Route object only in NTTCOM. Add it in the RIR database for the space.672 of 673
ROA: none182.255.10.0/24No ROA covers it. Add a ROA for AS55514, maxLength 24.672 of 673
Route object: RIR182.255.10.0/24Route object only in NTTCOM. Add it in the RIR database for the space.672 of 673

Route objects not announced

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

171.102.38.0/24APNIC, RADBValid
182.255.8.0/22NTTCOMNo ROA
182.255.12.0/23NTTCOMNo ROA
203.209.90.0/24APNIC, NTTCOMValid

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.