AS375
Operated by TIETOTIE-AS Tieto Oyj.
Summary
- // analyst note
- Legacy ASN served by RIPE NCC despite IANA block's historical 'Assigned by ARIN' annotation (RIPE-NCC-LEGACY-MNT present). RDAP timed out on the initial canonical fetch; re-run succeeded and returned clean top-level events[] (registration 2002-08-21, last changed 2026-01-15). Named upstream/peer ASNs not verified from a single first-party source this pass.
- // security note
- NEUTRAL/DATED: no notable public abuse signal for AS375's own address space as of 2026-07-02 (no Spamhaus SBL/DROP, no NANOG hijack/leak thread; valid RPKI on bgp.tools).
About this ASN.
AS375 is a legacy autonomous system number serving the network of Tieto Oyj — the Finnish IT software and consulting company known through most of the last decade as Tietoevry, which renamed back to Tieto Corporation on 30 March 2026. Although IANA block metadata annotates the surrounding number block (1–1876) as "Assigned by ARIN," the ASN is registered with and served by RIPE NCC today: RIPE RDAP is authoritative, carries the org handle ORG-TO27-RIPE, and the record shows the legacy maintainer RIPE-NCC-LEGACY-MNT consistent with a pre-RIR-split allocation later homed in the RIPE region. The autnum's top-level events give a registration date of 2002-08-21 and a last-changed date of 2026-01-15, and bgp.tools independently corroborates the 21 Aug 2002 registration. Routing-wise the AS is small but active: it originates roughly 52 IPv4 prefixes (about 87,040 addresses) plus one IPv6 prefix (2a03:9b80::/34), is broadly visible across RIS collectors (v4 seen by 323/323 peers), and has a CAIDA customer cone of a single ASN — itself — with two upstream providers and no downstream customers. Tieto is an IT-services company rather than a carrier or ISP, so it publishes no peering policy and has no PeeringDB entry; third-party observers classify the network as corporate/data-center infrastructure ("TIETO FIN DC CUSTOMER NETS"), not transit or eyeball. No notable abuse signal attaches to AS375's own address space — no Spamhaus SBL/DROP listing, no NANOG hijack/leak thread, valid RPKI on bgp.tools — though the parent company suffered an Akira ransomware attack on a Swedish data center in January 2024; that was a corporate compromise, not a documented abuse-of-AS375-prefixes routing event.
- Operator
- Tieto Oyj (English: Tieto Corporation; formerly Tietoevry Oyj until the 30 Mar 2026 rename), AS name TIETOTIE-AS, org handle ORG-TO27-RIPE [Confirmed] — rdap.db.ripe.net/autnum/375, tieto.com newsroom rename release, live.euronext.com filing 2026-03-30
- Country / RIR
- FI (Espoo), RIPE NCC [Confirmed] — rdap.db.ripe.net/autnum/375 (notices: Source=RIPE), RIPEstat abuse-contact-finder (authoritative_rir: ripe)
- Allocated
- 2002-08-21 (RIPE RDAP autnum top-level events, eventAction "registration", eventDate 2002-08-21T16:06:03Z — a first-party registry date, NOT an IEEE date); last changed 2026-01-15 [Confirmed] — rdap.db.ripe.net/autnum/375, corroborated by bgp.tools ("registered on 21 Aug 2002")
- Org status
- active, publicly traded — Tieto Oyj listed on Nasdaq Helsinki, Nasdaq Stockholm, and Oslo Børs; HQ Keilalahdentie 2-4, FI-02150 Espoo, Finland; ~EUR 1.8B revenue, ~13,000 employees, 20+ countries [Confirmed] — tieto.com/en/about-us, rdap.db.ripe.net/autnum/375
- Contacts
- abuse@tietoevry.com; official website https://www.tieto.com (www.tietoevry.com now 301-redirects there) [Confirmed] — RIPEstat abuse-contact-finder, tieto.com/en/about-us
Security/abuse context (NEUTRAL, DATED)
no notable public abuse signal for AS375's own address space as of 2026-07-02 (no Spamhaus SBL/DROP, no NANOG hijack/leak thread, valid RPKI on bgp.tools). Parent operator Tietoevry suffered an Akira ransomware attack on a Swedish data center 19–20 Jan 2024 — a corporate/data-center compromise, NOT a documented AS375-prefix routing/abuse event [Confirmed for the incident; distinction stated] — bgp.tools/as/375, spamhaus.org, bleepingcomputer.com Tietoevry-ransomware report, helpnetsecurity.com
Network & routing
- Network type
- corporate / data-center IT-services infrastructure (netblocks labeled "TIETO FIN DC CUSTOMER NETS"); not operator-published — third-party BGP observers tag it "Content" [Likely] — bgp.tools/as/375, ipinfo.io/AS375
- Size
- ~52 IPv4 prefixes / ~87,040 IPv4 addresses + 1 IPv6 prefix (2a03:9b80::/34); customer cone = 1 ASN (itself), 52 prefixes, 87,040 addresses [Confirmed] — stat.ripe.net routing-status, api.asrank.caida.org/v2/restful/asns/375
- Routing/peering
- 2 upstream providers, 0 peers, 0 customers (CAIDA asnDegree.provider=2); RIPEstat observed_neighbours=2. Named upstream ASNs not verified from a single first-party source [Likely] — api.asrank.caida.org/v2/restful/asns/375, bgp.tools/as/375, ipinfo.io/AS375
- Peering policy
- none published — no PeeringDB entry, no peering page (an IT-services company, not a carrier; genuine sourced absence, not a search failure) [Likely] — peeringdb.com/asn/375, tieto.com/en/about-us
- RPKI
- bgp.tools shows valid RPKI on announced prefixes; per-prefix RIPEstat rpki-validation not run this pass (endpoint requires a --prefix parameter) [Likely] — bgp.tools/as/375
- Notable usage
- corporate/data-center infrastructure supporting Tieto's own IT and software services; no operator-published notable-usage statement found [Unknown] — ipinfo.io/AS375, bgp.tools/as/375
- Related ASNs
- AS5411 (Tieto Sweden) exists as a separate ASN [Likely] — api.asrank.caida.org/v2/restful/asns/375
- BGP visibility
- IPv4 seen by 323/323 RIS peers, IPv6 by 320/322; CAIDA global AS rank 13,300 [Confirmed] — stat.ripe.net routing-status, api.asrank.caida.org/v2/restful/asns/375
- Analyst note
- RDAP timed out on the initial canonical fetch; re-run of fetch-canonical.mjs succeeded and returned the full autnum with clean top-level events[]. RIR is RIPE NCC despite the IANA block's historical "Assigned by ARIN" annotation. The 2026-01-15 last-changed predates the 30 Mar 2026 corporate rename yet the record already reads Tieto Oyj — a discrepancy worth noting, not resolvable from RDAP alone.
What this network routes.
- 131.207.0.0/17
- 192.49.192.0/18
- 192.49.96.0/20
- 192.49.176.0/20
- 192.49.160.0/21
- 192.49.56.0/21
- 192.49.40.0/21
- 192.49.0.0/21
- 192.49.152.0/21
- 192.49.92.0/22
- 192.49.120.0/22
- 192.49.48.0/22
- 192.49.128.0/22
- 192.49.112.0/22
- 192.49.64.0/22
- 192.49.36.0/22
- 192.49.148.0/22
- 192.49.86.0/23
- 192.49.52.0/23
- 192.49.88.0/23
- 192.49.72.0/23
- 192.49.136.0/23
- 192.49.174.0/23
- 192.49.70.0/23
- 192.49.140.0/23
- 192.49.124.0/23
- 192.49.168.0/23
- 192.49.13.0/24
- 192.49.81.0/24
- 192.49.173.0/24
- 192.49.134.0/24
- 192.49.22.0/24
- 192.49.142.0/24
- 192.49.55.0/24
- 192.49.170.0/24
- 192.49.91.0/24
- 192.49.117.0/24
- 192.49.68.0/24
- 192.49.133.0/24
- 192.49.139.0/24
- 192.49.144.0/24
- 192.49.146.0/24
- 192.49.78.0/24
- 192.49.20.0/24
- 192.49.126.0/24
- 192.49.9.0/24
- 192.49.19.0/24
- 192.49.33.0/24
- 192.49.72.0/24
- 192.49.10.0/24
- 192.163.145.0/24
- 192.49.119.0/24
- 2a03:9b80::/34
Who it talks to.
| ASN | Operator | Role |
|---|---|---|
| AS55002 | — | upstream |
| AS12552 | — | upstream |