bgpreport

Network · data from 2026-11-12

AS149766 Y.U.T Corporate (NIX/ISP)

Registry name: YUT-AS-AP - Y.U.T Corporate Company Limited, TH · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS149766, 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.
46.37.121.0/24 Invalid: origin Other origin only 1 0%low visibility 1
44.32.80.0/21 No ROA Other IRR onlyRADB 671 100% 66
81.31.234.0/24 Valid RIR databaseRADB, RIPE 671 100% 66
103.185.146.0/23 Valid RIR databaseAPNIC, RADB 671 100% 66
103.185.146.0/24 Valid RIR databaseAPNIC, RADB 671 100% 66
103.185.147.0/24 Valid RIR databaseAPNIC, RADB 671 100% 66
103.203.42.0/24 Valid RIR databaseRADB, RIPE 671 100% 66
140.150.152.0/24 Valid RIR databaseRADB, RIPE 671 100% 66
151.244.255.0/24 Valid RIR databaseRADB, RIPE 671 100% 66
185.84.160.0/23 Valid RIR databaseRADB, RIPE 671 100% 66
185.84.160.0/24 Valid RIR databaseRIPE 671 100% 66
185.84.161.0/24 Valid RIR databaseRIPE 671 100% 66
2401:93e0::/32 Valid RIR databaseAPNIC 634 100% 67

AS-SET

PeeringDB's irr_as_set for AS149766: AS149766:AS-CUSTOMERS. 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 (AS149766 isn't in the set, or no route object for AS149766 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 objectsAS149766 in itNot covered
AS149766:AS-CUSTOMERS APNIC 3231 Yes 1

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

  • ROA: origin1
  • ROA: none1
  • Route object: none1
  • Route object: RIR1
ChangePrefix or setDetailFull-table peers
ROA: origin46.37.121.0/24ROAs covering it name AS834, not AS149766. If AS149766 should announce it, add a ROA for AS149766.1 of 673
Route object: none46.37.121.0/24Route objects for it name AS834. Add a route object with origin AS149766 in the RIR database for the space.1 of 673
ROA: none44.32.80.0/21No ROA covers it. Add a ROA for AS149766, maxLength 21.671 of 673
Route object: RIR44.32.80.0/21Route object only in RADB. Add it in the RIR database for the space.671 of 673

Route objects not announced

Every route object with origin AS149766 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.