AS1050
AS1050 announces 2 IPv4 and 3 IPv6 prefixes and peers with 2 other networks.
Summary
- // analyst note
- Routing values are a combined observation from route-views2 and route-views6 at 2026-11-01T00:00:00.000Z. AS_PATH neighbours are not verified peers or commercial relationships. The snapshot does not establish current activity, ownership, location, legitimacy, or security.
- // security note
- The AS1050 peering page says peer routes are filtered using valid IRR objects and RPKI-invalid routes are rejected, with valid and unknown RPKI states permitted.
About this ASN.
AS1050 is an ASN with observed routes in the 2026-11-01 00:00 UTC combined Route Views snapshot; its operator and deployment status are unknown. The snapshot from route-views2 and route-views6 contains 2 IPv4 prefixes, an estimated 512 IPv4 addresses, and 3 IPv6 prefixes. It also shows two AS_PATH neighbours, AS53667 and AS399646. These observations describe that snapshot, not current activity or commercial relationships.
The AS1050 peering page describes route-filtering practices, including filtering peer routes using valid IRR objects, rejecting RPKI-invalid routes, and accepting valid or unknown RPKI states. It also lists controls for bogons, small prefixes, route leaks, graceful shutdown, and blackholing. To identify a network using this ASN, compare its observed prefixes and paths against a fresh routing snapshot, then independently check registry and IRR records. The supplied evidence does not link an operator, location, product, or security reputation to AS1050.
- Routing snapshot
- Two IPv4 prefixes and three IPv6 prefixes observed in the combined 2026-11-01 00:00 UTC Route Views data.
- Triage
- Operator identity and present deployment status are unknown; the snapshot alone does not establish either.
- Identification
- Compare candidate prefixes and AS_PATHs against a fresh routing view, then corroborate with registry and IRR records.
- Route handling
- The peering page documents IRR-based filtering and rejection of RPKI-invalid routes.
- RIR
- ARIN, allocating RIR for the IANA ASN block [Confirmed] — https://www.iana.org/assignments/as-numbers/as-numbers-1.csv
- Operator
- Unknown [Unknown]
- AS name
- Unknown [Unknown]
- Country
- Unknown [Unknown]
- Website
- Unknown [Unknown]
Network & routing
- Routing snapshot
- 2 IPv4 prefixes; estimated 512 IPv4 addresses; 3 IPv6 prefixes, combined across route-views2 and route-views6 at 2026-11-01 00:00 UTC [Confirmed] — https://archive.routeviews.org/route-views2/bgpdata/2026.11/RIBS/rib.20261101.0000.bz2
- ASN
- 1050 [Confirmed] — https://www.iana.org/assignments/as-numbers/as-numbers-1.csv
- Assignment class
- Unknown [Unknown]
- AS_PATH neighbours
- 2 observed; sample AS53667 and AS399646 [Confirmed] — https://archive.routeviews.org/route-views6/bgpdata/2026.11/RIBS/rib.20261101.0000.bz2
What this network routes.
- 136.175.104.0/24
- 44.31.183.0/24
- 2602:fb3f::/40
- 2602:fb3f:1::/48
- 2602:fb3f:2::/48
Who it talks to.
Neighbours observed by RouteViews at 2026-11-06, lowest ASN first. Relationships are inferences from the CAIDA AS Relationships Dataset, 2026-08-01, and establish no commercial arrangement; a dash means the inference did not resolve.
| ASN | Operator | Role |
|---|---|---|
| AS53667 | FranTech Solutions | — |
| AS399646 | — | — |