bgpreport

Network · data from 2026-11-12

AS139657 UNINET-AS-UTCC - University of the Thai Chamber of Commerce

Registry name: UNINET-AS-UTCC - University of the Thai Chamber of Commerce, TH · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS139657, 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.
2001:3c8:10ff::/48 Invalid: origin None 75 12% 44
202.28.8.0/21 No ROA Other origin only 670 100% 69
202.28.8.0/23 No ROA Other origin only 670 100% 67
202.28.10.0/23 No ROA Other origin only 670 100% 67
202.28.12.0/23 No ROA Other origin only 670 100% 67
202.28.14.0/23 No ROA Other origin only 670 100% 67

AS-SET

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

  • ROA: origin1
  • ROA: none5
  • Route object: none6
ChangePrefix or setDetailFull-table peers
ROA: origin2001:3c8:10ff::/48ROAs covering it name AS4621, not AS139657. If AS139657 should announce it, add a ROA for AS139657.75 of 636
Route object: none2001:3c8:10ff::/48No route object for it. Add a route object with origin AS139657 in the RIR database for the space.75 of 636
ROA: none202.28.8.0/21No ROA covers it. Add a ROA for AS139657, maxLength 21.670 of 673
Route object: none202.28.8.0/21Route objects for it name AS4750, AS7470, AS9741, AS38082, AS58806. Add a route object with origin AS139657 in the RIR database for the space.670 of 673
ROA: none202.28.8.0/23No ROA covers it. Add a ROA for AS139657, maxLength 23.670 of 673
Route object: none202.28.8.0/23Route objects for it name AS7470, AS38082, AS58806. Add a route object with origin AS139657 in the RIR database for the space.670 of 673
ROA: none202.28.10.0/23No ROA covers it. Add a ROA for AS139657, maxLength 23.670 of 673
Route object: none202.28.10.0/23Route objects for it name AS7470, AS38082, AS58806. Add a route object with origin AS139657 in the RIR database for the space.670 of 673
ROA: none202.28.12.0/23No ROA covers it. Add a ROA for AS139657, maxLength 23.670 of 673
Route object: none202.28.12.0/23Route objects for it name AS7470, AS38082, AS58806. Add a route object with origin AS139657 in the RIR database for the space.670 of 673
ROA: none202.28.14.0/23No ROA covers it. Add a ROA for AS139657, maxLength 23.670 of 673
Route object: none202.28.14.0/23Route objects for it name AS7470, AS38082, AS58806. Add a route object with origin AS139657 in the RIR database for the space.670 of 673

Route objects not announced

Every route object with origin AS139657 is announced.

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.