Network · data from 2026-11-12
AS132637 BITSNETID
Registry name: BITSNET-AS-ID - PT BINA INFORMATIKA SOLUSI, ID · PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS132637, 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.19.56.0/24 | Valid | Nonecovered by 103.19.56.0/22 | 673 100% |
| 103.19.57.0/24 | Valid | Nonecovered by 103.19.56.0/22 | 673 100% |
| 103.19.58.0/24 | Valid | Nonecovered by 103.19.56.0/22 | 673 100% |
| 103.19.59.0/24 | Valid | Nonecovered by 103.19.56.0/22 | 673 100% |
| 103.143.244.0/24 | Valid | RIR databaseAPNIC | 673 100% |
| 103.143.245.0/24 | Valid | RIR databaseAPNIC | 673 100% |
| 2405:60c0::/32 | Valid | RIR databaseAPNIC | 636 100% |
| 2402:32c0::/32 | Valid | RIR databaseAPNIC | 635 100% |
AS-SET
PeeringDB's irr_as_set for AS132637: AS132637:AS-BITSNET. 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 (AS132637 isn't in the set, or no route object for AS132637 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 | AS132637 in it | Not covered | |
|---|---|---|---|---|---|---|
| AS132637:AS-BITSNET | In no IRR database read today. | |||||
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.
- Route object: none4
- AS-SET: not found1
- Route object: not announced5
| Change | Prefix or set | Detail |
|---|---|---|
| Route object: none | 103.19.56.0/24 | No route object for it. A route object for 103.19.56.0/22 with origin AS132637 covers it (filters allowing more-specifics accept it). Add a route object with origin AS132637 in the RIR database for the space. |
| Route object: none | 103.19.57.0/24 | No route object for it. A route object for 103.19.56.0/22 with origin AS132637 covers it (filters allowing more-specifics accept it). Add a route object with origin AS132637 in the RIR database for the space. |
| Route object: none | 103.19.58.0/24 | No route object for it. A route object for 103.19.56.0/22 with origin AS132637 covers it (filters allowing more-specifics accept it). Add a route object with origin AS132637 in the RIR database for the space. |
| Route object: none | 103.19.59.0/24 | No route object for it. A route object for 103.19.56.0/22 with origin AS132637 covers it (filters allowing more-specifics accept it). Add a route object with origin AS132637 in the RIR database for the space. |
| AS-SET: not found | AS132637:AS-BITSNET | PeeringDB names AS132637:AS-BITSNET; no IRR database read has it. |
Route objects not announced
Route objects with origin AS132637 whose prefix no peer sees AS132637 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 103.19.56.0/22 | APNIC | Valid |
| 103.80.238.0/23 | REACH | Invalid: origin |
| 103.80.238.0/24 | REACH | Invalid: origin |
| 103.80.239.0/24 | REACH | Invalid: origin |
| 103.143.244.0/23 | 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.