Network · data from 2026-11-12
AS133968 Logon Broadband
Registry name: LOGON-AS-IN - Logon Broadband, IN · PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS133968, 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.133.168.0/24 | Valid | RIR databaseAPNIC | 672 100% |
| 103.133.169.0/24 | Valid | RIR databaseAPNIC | 672 100% |
| 103.133.170.0/24 | Valid | RIR databaseAPNIC | 672 100% |
| 103.133.171.0/24 | Valid | RIR databaseAPNIC | 672 100% |
| 103.158.244.0/24 | Valid | RIR databaseAPNIC | 672 100% |
| 103.158.245.0/24 | Valid | RIR databaseAPNIC | 672 100% |
| 103.203.228.0/24 | Valid | RIR databaseAPNIC | 672 100% |
| 103.203.229.0/24 | Valid | RIR databaseAPNIC | 672 100% |
| 103.203.230.0/24 | Valid | RIR databaseAPNIC | 672 100% |
| 103.203.231.0/24 | Valid | RIR databaseAPNIC | 672 100% |
| 2001:df2:100::/48 | Valid | RIR databaseAPNIC | 636 100% |
AS-SET
PeeringDB's irr_as_set for AS133968: AS133968:AS-LOGON. 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 (AS133968 isn't in the set, or no route object for AS133968 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 | AS133968 in it | Not covered |
|---|---|---|---|---|---|
| AS133968:AS-LOGON | APNIClists itself further down5 member sets in no database: AS-6186, AS-HNSISP-TRANSIT, AS136346:AS-FASTTNET, AS137609:AS-DCSISPL, AS214174:AS-RIPE | 1,262 | 144 | Yes | 0 |
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 10 are in fix.csv.
- AS-SET: missing member5
- Route object: not announced5
| Change | Prefix or set | Detail |
|---|---|---|
| AS-SET: missing member | AS133968:AS-LOGON | AS133968:AS-LOGON (APNIC) lists AS-6186; no IRR database read has it. |
| AS-SET: missing member | AS133968:AS-LOGON | AS133968:AS-LOGON (APNIC) lists AS-HNSISP-TRANSIT; no IRR database read has it. |
| AS-SET: missing member | AS133968:AS-LOGON | AS133968:AS-LOGON (APNIC) lists AS136346:AS-FASTTNET; no IRR database read has it. |
| AS-SET: missing member | AS133968:AS-LOGON | AS133968:AS-LOGON (APNIC) lists AS137609:AS-DCSISPL; no IRR database read has it. |
| AS-SET: missing member | AS133968:AS-LOGON | AS133968:AS-LOGON (APNIC) lists AS214174:AS-RIPE; no IRR database read has it. |
Route objects not announced
Route objects with origin AS133968 whose prefix no peer sees AS133968 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 103.133.168.0/22 | APNIC | Valid |
| 103.133.168.0/23 | APNIC | Valid |
| 103.133.170.0/23 | APNIC | Valid |
| 103.158.244.0/23 | APNIC | Valid |
| 103.203.228.0/22 | 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.