bgpreport

Network · data from 2026-11-12

AS133880 REDCROSS-AS-AP - The Thai Red Cross Society

Registry name: REDCROSS-AS-AP - The Thai Red Cross Society, TH · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS133880, 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.44.216.0/22 No ROA Other IRR onlyNTTCOM 673 100% 69
103.44.216.0/23 No ROA Other IRR onlyNTTCOM 673 100% 69
103.44.218.0/23 No ROA Other IRR onlyNTTCOM 673 100% 69
45.125.230.0/23 No ROA Other IRR onlyRADB 145 22% 51
45.125.229.0/24 Valid RIR databaseAPNIC, RADB 673 100% 69
45.125.230.0/24 Valid RIR databaseAPNIC, RADB 673 100% 69
45.125.231.0/24 Valid RIR databaseAPNIC, RADB 673 100% 69
103.44.216.0/24 Valid RIR databaseAPNIC, NTTCOM, RADB 673 100% 69
103.44.217.0/24 Valid RIR databaseAPNIC, NTTCOM, RADB 673 100% 69
103.44.218.0/24 Valid RIR databaseAPNIC, NTTCOM, RADB 673 100% 69
103.44.219.0/24 Valid RIR databaseAPNIC, NTTCOM, RADB 673 100% 69
45.125.228.0/24 Valid RIR databaseAPNIC, RADB 132 20% 49
2401:d880::/32 Valid RIR databaseAPNIC, RADB 39 6%low visibility 29

AS-SET

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

  • ROA: none4
  • Route object: RIR4
  • Route object: not announced1
ChangePrefix or setDetailFull-table peers
ROA: none103.44.216.0/22No ROA covers it. Add a ROA for AS133880, maxLength 22.673 of 673
Route object: RIR103.44.216.0/22Route object only in NTTCOM. Add it in the RIR database for the space.673 of 673
ROA: none103.44.216.0/23No ROA covers it. Add a ROA for AS133880, maxLength 23.673 of 673
Route object: RIR103.44.216.0/23Route object only in NTTCOM. Add it in the RIR database for the space.673 of 673
ROA: none103.44.218.0/23No ROA covers it. Add a ROA for AS133880, maxLength 23.673 of 673
Route object: RIR103.44.218.0/23Route object only in NTTCOM. Add it in the RIR database for the space.673 of 673
ROA: none45.125.230.0/23No ROA covers it. Add a ROA for AS133880, maxLength 23.145 of 673
Route object: RIR45.125.230.0/23Route object only in RADB. Add it in the RIR database for the space.145 of 673

Route objects not announced

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

45.125.228.0/22RADBNo 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.