bgpreport

Network · data from 2026-11-12

AS45642 JTIX Route Servers L2 / JasTel NIX L3

Registry name: JASTEL-NETWORK-TH-NIX-AP - Jasmine International Tower, TH · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS45642, 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.
58.82.178.0/24 Valid RIR databaseAPNIC 6 1%low visibility 4
203.147.13.0/24 Valid RIR databaseAPNIC 6 1%low visibility 4
218.100.66.0/24 Valid RIR databaseAPNIC 6 1%low visibility 4

AS-SET

PeeringDB's irr_as_set for AS45642: AS-45642. 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 (AS45642 isn't in the set, or no route object for AS45642 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 objectsAS45642 in itNot covered
AS-45642 RADB 93110,643 No 3

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

  • AS-SET: own ASN1
ChangePrefix or setDetailFull-table peers
AS-SET: own ASNAS-45642AS45642 isn't in AS-45642 (RADB) once expanded. Add AS45642 to it.

Route objects not announced

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