Konfidenz
35- Informationstyp
- Dieser Datensatz bewahrt die Organisationsidentität von Interconnect Systems und lässt rechtliche Einheit, Netzwerkressourcen, Serviceumfang, Führung sowie zugehörige öffentliche Quellen für Ergänzungen offen.
Zugehörige Details
RIPE lookup for ISN36-RIPE is the official public registry path for verifying the Interconnect Systems NOC role object and its linked maintainer/contact metadata.
Öffentliche Quelle
RIPE lookup for AS212053 is the official public registry path for verifying the SHIJITONG aut-num, ORG-ST398-RIPE association, listed import/export counterparties, status, and created/modified dates.
Öffentliche Quelle
RIPE lookup for ORG-ST398-RIPE is the official public registry path for verifying the ShiJI Tong organisation object, country field, org-type, and maintainer references.
Öffentliche Quelle
IPIP reproduces RIPE-derived whois for AS212053, including AS name SHIJITONG, org-name ShiJI Tong, ORG-ST398-RIPE, imports from AS34872 and AS20473, and the Interconnect Systems NOC role object.
routing and whois aggregator
BGP.he lists AS212053 as ShiJI Tong, country of origin China, and shows current BGP-originated prefix counts, RPKI validation status, observed peers, and a RIPE-derived aut-num block updated on .
bgp observability source
Cloudflare Radar identifies AS212053 as SHIJITONG with country or territory China and provides AS-level routing, traffic, quality, adoption, and security views.
internet measurement platform
IPIP's 2a0e:7d45::/32 page shows netname Customer-Shiji-Tong-20251025, org ORG-ST398-RIPE, admin-c and tech-c ISN36-RIPE, and a route6 origin of AS20473, tying the role to a related IPv6 resource context while keeping the origin separate from AS212053.
routing and whois aggregator
IPGeolocation lists AS212053 as SHIJITONG, organization ShiJI Tong, registry RIPE, allocation status ASSIGNED, and date allocated , but its route counts differ from BGP.he and IPIP.
asn intelligence aggregator
Cloudflare Radar routing page identifies AS212053 SHIJITONG and provides routing statistics, announced IP address space, prefix, connectivity, BGP announcement, and IRR AS-SET views.
routing observability dataset
TheIpAPI lists AS212053 as SHIJITONG and RIPE-registered but reports a different organisation label, country, creation date, and prefix counts from other public datasets, supporting the watchpoint that third-party ASN snapshots disagree.
third party asn dataset
NetworksDB identifies AS212053 as SHIJITONG for ShiJi Tong in China but reports no IPv4 announcements in its snapshot, another example of public route-count disagreement.
third party asn dataset
IPIP's related IPv6 resource page shows netname Customer-Shiji-Tong-20251025, org ORG-ST398-RIPE, admin-c and tech-c ISN36-RIPE, and route6 origin AS20473, tying the role to related number-resource administration while keeping that route origin separate from AS212053.
third party ripe whois mirror
- RIPE role-object documentation
RIPE documentation explains that a role object describes a business function or operational unit, has a unique NIC handle, and is referenced by NIC handle rather than by role name.
official registry documentation
RIPE documentation explains that role objects describe roles performed by one or more people and that their primary key is the nic-hdl attribute, supporting the distinction between role/contact metadata and standalone institution identity.
official registry documentation
RIPE documentation describes the aut-num object as both Internet Number Registry data and Internet Routing Registry data for an autonomous system, including routing-policy attributes such as import and export.
official registry documentation
IPinfo identifies AS212053 as ShiJI Tong in China, shows registry RIPE, allocation date , no hosted domains, and a route snapshot that differs from other datasets.
asn intelligence dataset
IP2Location identifies AS212053 as Shiji Tong in China, reports alicenetworks.net as a domain name and lists an address-space snapshot that differs from IPIP and IPinfo.
asn intelligence dataset
RIPE REST API documentation states that RIPE Database objects have unique locator URIs and that the nic-hdl attribute is the key for person and role object lookups.
official documentation
RIPE Database documentation describes role objects and organisation objects in the registry data model, including role-object use for operational groups and org-type OTHER as a broad category.
official registry documentation
2ip reproduces a RIPE-derived AS212053 record showing SHIJITONG, ShiJI Tong, ORG-ST398-RIPE, ISN36-RIPE, RIPE-NCC-END-MNT, SERVPERSO-MNT, IS-MNT, and import/export policy references.
third party ripe derived whois mirror
RIPE documentation states that authorised users can create, modify, or delete RIPE Database objects and that processing applies syntax, authorisation, referential-integrity, and policy checks.
official documentation
RIPE documentation describes role objects as roles performed by one or more people, such as a help desk, network monitoring centre, or administrator team, and states that role objects use nic-hdl as the primary key.
official documentation
routing rank list
RIPE documentation describes a role object as a role performed by one or more people, such as a help desk, network monitoring centre, or administrator team, and explains that role objects use nic-hdl as the primary key.
official documentation
RIPE documentation describes the organisation object as a record for an organisation that has registered an Internet resource, and notes that it may represent a company, non-profit group, or individual.
official documentation
RIPE documentation describes the aut-num object as both ASN registration detail and Internet Routing Registry routing policy, supporting the interpretation of AS212053 as routing context rather than the subject object itself.
official documentation
RIPE documentation explains that mntner objects protect database objects and contain authentication information required to authorise creation, deletion, or modification of protected objects.
official documentation
RIPE documentation explains that mntner references define authorisation for operations on database objects and that updates require a valid credential for a relevant maintainer object.
official documentation
BGP.he's 2.26.199.0/24 page shows a less-specific AS212053 announcement for 2.26.192.0/21 marked with IRR origin mismatch and ROA signed invalid status on a page updated on .
routing observability
A Larus search hit in APNIC Labs I-RoV metrics identifies AS17561 as LCS-AS-AP LARUS Limited, a separate routing context from AS212053 SHIJITONG.
routing measurement
- PeeringDB AS17561 LARUS Limited
PeeringDB identifies AS17561 as LARUS Limited with website larus.net and IRR as-set AS-LARUS, supporting the boundary that visible Larus evidence belongs to a separate routing object from AS212053 and ISN36-RIPE.
public interconnection registry
Cloudflare Radar identifies AS17561 as LCS-AS-AP with AKA LARUS Limited, country or territory Hong Kong, and website larus.net, again placing Larus in a separate AS17561 context.
public routing observability dataset
LARUS Limited's public website describes IP address management, IP address provisioning, RIR membership application and management, and infrastructure services; it does not verify a tie to Interconnect Systems NOC or AS212053 in the reviewed material.
operator website
RIPE Database documentation states that the database provides the public view of Internet resource information, supports the RIPE number registry and routing registry, and facilitates coordination between network operators.
official documentation
RIPE RDAP documentation describes the public RDAP paths for autnum and entity objects, with entity covering PERSON, ROLE, ORGANISATION, and MNTNER objects.
official documentation
Zuletzt aktualisiert: 2026-06-01