Network · data from 2026-11-12
AS154648 TermRat Network
Registry name: TERMRATNETWORKLIMITED-AS-AP - TermRat Network Limited, CN · PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS154648, 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.
| 31.77.184.0/24 | Valid | Nonecovered by 31.77.184.0/23 | 671 100% |
| 31.77.185.0/24 | Valid | Nonecovered by 31.77.184.0/23 | 671 100% |
| 87.84.190.0/24 | Valid | Nonecovered by 87.84.190.0/23 | 532 79% |
| 87.84.191.0/24 | Valid | Nonecovered by 87.84.190.0/23 | 532 79% |
| 31.77.186.0/24 | Valid | Nonecovered by 31.77.186.0/23 | 531 79% |
| 31.77.187.0/24 | Valid | Nonecovered by 31.77.186.0/23 | 531 79% |
| 31.77.184.0/23 | Valid | RIR databaseRIPE | 671 100% |
| 141.11.219.0/24 | Valid | RIR databaseRADB, RIPE | 671 100% |
| 31.77.186.0/23 | Valid | RIR databaseRIPE | 663 99% |
| 87.84.190.0/23 | Valid | RIR databaseRIPE | 663 99% |
| 2a13:9500:194::/48 | Valid | RIR databaseRIPE | 634 100% |
AS-SET
PeeringDB's irr_as_set for AS154648: AS154648:AS-SET. 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 (AS154648 isn't in the set, or no route object for AS154648 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.
| Name | Database | ASNs | Sets | AS154648 in it | Not covered |
|---|---|---|---|---|---|
| AS154648:AS-SET | APNIC | 859 | 18 | No | 11 |
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.
- Route object: none6
- AS-SET: own ASN1
- Route object: not announced2
| Change | Prefix or set | Detail |
|---|---|---|
| Route object: none | 31.77.184.0/24 | No route object for it. A route object for 31.77.184.0/23 with origin AS154648 covers it (filters allowing more-specifics accept it). Add a route object with origin AS154648 in the RIR database for the space. |
| Route object: none | 31.77.185.0/24 | No route object for it. A route object for 31.77.184.0/23 with origin AS154648 covers it (filters allowing more-specifics accept it). Add a route object with origin AS154648 in the RIR database for the space. |
| Route object: none | 87.84.190.0/24 | No route object for it. A route object for 87.84.190.0/23 with origin AS154648 covers it (filters allowing more-specifics accept it). Add a route object with origin AS154648 in the RIR database for the space. |
| Route object: none | 87.84.191.0/24 | No route object for it. A route object for 87.84.190.0/23 with origin AS154648 covers it (filters allowing more-specifics accept it). Add a route object with origin AS154648 in the RIR database for the space. |
| Route object: none | 31.77.186.0/24 | No route object for it. A route object for 31.77.186.0/23 with origin AS154648 covers it (filters allowing more-specifics accept it). Add a route object with origin AS154648 in the RIR database for the space. |
| Route object: none | 31.77.187.0/24 | No route object for it. A route object for 31.77.186.0/23 with origin AS154648 covers it (filters allowing more-specifics accept it). Add a route object with origin AS154648 in the RIR database for the space. |
| AS-SET: own ASN | AS154648:AS-SET | AS154648 isn't in AS154648:AS-SET (APNIC) once expanded. Add AS154648 to it. |
Route objects not announced
Route objects with origin AS154648 whose prefix no peer sees AS154648 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 82.109.224.0/22 | RADB | Valid |
| 163.223.173.0/24 | APNIC | Valid |
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.