Skip to main content

AS35087

NTSI-AS

--------------------------------------------------------------

Registry

Authoritative registration data

AS number
35087
Name
NTSI-AS
Organisation
--------------------------------------------------------------
Country
RIR
RIPE
Registered
Source:asn:rdap retrieved

IPv4 prefixes

2

IPv6 prefixes

1

Total announced

3

Announced prefixes

Observed in BGP by route collectors, not a registry allocation list

Prefixes announced by AS35087
109.68.16.0/21 IPv4 /21 not checked
85.119.72.0/21 IPv4 /21 not checked
2a02:548::/32 IPv6 /32 not checked

No rows match “”.

Showing of

Source:ripestat:announced-prefixes observed

Internet Exchanges

Exchanges where this network has a listed peering LAN connection

No Internet Exchange memberships found

The exchange directory has no current membership records for this AS.

Source:peeringdb retrieved

Exchange membership means the network has a listed connection; it does not prove peering with other members.

Observed adjacencies

Networks seen next to AS35087 in BGP paths by route collectors.

Source:ripestat:asn-neighbours observed

Observed upstreams

5 networks seen before AS35087 in AS paths

Observed upstreams
Families
AS31133 MF-MGSM-AS 345 647
v4 v6
AS35598 339 637
v4
AS62255 BEMYLINK 110 189
v4
AS25091 IP-Max 5 17
v4 v6
AS9198 KAZTELECOM-AS 1 1
v6

No rows match “”.

Showing of

Observed downstreams

2 networks seen after AS35087 in AS paths

Observed downstreams
Families
AS47785 292 381
v4
AS31133 MF-MGSM-AS 17 21
v4

No rows match “”.

Showing of

Uncertain adjacencies

9 adjacencies that may be an artefact of collector peering

Uncertain adjacencies
Families
AS24482 SGGS-AS-AP 2 12
v4 v6
AS49544 i3Dnet 2 6
v4
AS199524 GCORE 3 5
v4
AS28917 Fiord-AS 2 5
v4 v6
AS36236 NETACTUATE 2 4
v4 v6
AS41327 FIBERTELECOM-AS 2 4
v4 v6
AS41722 2 4
v4 v6
AS49673 TRUENETWORK 2 3
v4
AS28910 1 1
v6

No rows match “”.

Showing of

Note:
These are observed adjacencies derived from BGP path data, not confirmed commercial relationships. A network appearing before another in an AS path does not establish that it is a paying transit customer, a settlement free peer, or anything else contractual. Adjacencies marked uncertain were seen only as direct peers of a route collector, so the collector's own peering may have created them.