Skip to main content

AS31376

SMART-AS

++ UPSTREAMS ++

Registry

Authoritative registration data

AS number
31376
Name
SMART-AS
Organisation
++ UPSTREAMS ++
Country
RIR
RIPE
Registered
Source:asn:rdap retrieved

IPv4 prefixes

25

IPv6 prefixes

1

Total announced

26

Announced prefixes

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

Prefixes announced by AS31376
217.119.16.0/20 IPv4 /20 not checked
80.249.176.0/20 IPv4 /20 not checked
80.73.192.0/20 IPv4 /20 not checked
109.71.176.0/21 IPv4 /21 not checked
188.93.240.0/21 IPv4 /21 not checked
213.108.32.0/21 IPv4 /21 not checked
80.79.240.0/21 IPv4 /21 not checked
91.190.80.0/21 IPv4 /21 not checked
93.190.224.0/21 IPv4 /21 not checked
93.92.192.0/21 IPv4 /21 not checked
94.125.8.0/21 IPv4 /21 not checked
185.155.112.0/22 IPv4 /22 not checked
185.42.60.0/22 IPv4 /22 not checked
80.79.248.0/22 IPv4 /22 not checked
91.219.180.0/22 IPv4 /22 not checked
195.191.146.0/23 IPv4 /23 not checked
195.93.206.0/23 IPv4 /23 not checked
80.79.252.0/23 IPv4 /23 not checked
91.215.252.0/23 IPv4 /23 not checked
193.110.237.0/24 IPv4 /24 not checked
193.26.214.0/24 IPv4 /24 not checked
193.46.2.0/24 IPv4 /24 not checked
91.198.130.0/24 IPv4 /24 not checked
91.215.254.0/24 IPv4 /24 not checked
194.153.158.128/25 IPv4 /25 not checked
2a02:16e8::/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

Internet Exchange memberships listed for AS31376
Address families
CLOUD-IX SPB 1,000 Mbps IPv4 · IPv6
GNM-IX 40,000 Mbps IPv4 · IPv6
MSK-IX Saint-Petersburg: MSK-IX Saint-Petersburg peering network 20,000 Mbps IPv4 · IPv6
PITER-IX Frankfurt 200,000 Mbps IPv4
PITER-IX Helsinki 200,000 Mbps IPv4
PITER-IX Moscow: MSK_PEERING_VLAN 200,000 Mbps IPv4 · IPv6
PITER-IX Saint-Petersburg: SPB_PEERING_VLAN 200,000 Mbps IPv4 · IPv6

No rows match “”.

Showing of

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 AS31376 in BGP paths by route collectors.

Source:ripestat:asn-neighbours observed

Observed upstreams

20 networks seen before AS31376 in AS paths

Observed upstreams
Families
AS20764 RASCOM-AS 1,495 4,559
v4 v6
AS9002 RETN-AS 1,088 4,335
v4 v6
AS31500 1,035 3,473
v4 v6
AS31133 705 1,749
v4 v6
AS6939 HURRICANE 283 859
v4
AS8218 NEO-ASN 47 452
v4 v6
AS25091 IP-Max 68 334
v4 v6
AS47692 40 205
v4 v6
AS137409 GSLNETWORKS-AS-AP 32 136
v4
AS41327 FIBERTELECOM-AS 36 99
v4 v6
AS42295 TBISS-AS 34 96
v4
AS15958 22 58
v4
AS50673 20 56
v4
AS9198 18 54
v4 v6
AS39351 ESAB-AS 18 51
v4 v6
AS6663 19 50
v4 v6
AS56655 GIGAHOST 19 50
v4
AS60171 17 48
v4 v6
AS57304 16 41
v4
AS33891 CORE-BACKBONE 8 10
v4

No rows match “”.

Showing of

Observed downstreams

23 networks seen after AS31376 in AS paths

Observed downstreams
Families
AS215179 375 2,478
v4
AS33908 571 1,254
v4
AS203668 300 710
v4
AS210447 256 610
v4
AS44899 288 357
v4
AS199007 288 357
v4
AS202510 288 357
v4
AS208615 288 357
v4
AS216011 288 357
v4
AS42301 285 354
v4
AS213411 286 353
v4
AS208511 267 334
v4
AS49994 109 235
v4
AS209096 115 143
v4
AS202082 113 142
v4
AS51667 109 128
v4
AS211185 91 115
v4
AS50082 82 103
v4
AS56619 60 82
v4
AS47333 33 43
v4
AS202650 19 33
v4
AS212423 11 17
v4
AS212452 11 17
v4

No rows match “”.

Showing of

Uncertain adjacencies

17 adjacencies that may be an artefact of collector peering

Uncertain adjacencies
Families
AS24482 SGGS-AS-AP 19 339
v4 v6
AS208972 22 59
v4 v6
AS3170 21 58
v4 v6
AS44901 21 57
v4
AS200612 22 55
v4
AS205112 PHILUNET 22 54
v4 v6
AS209823 22 54
v4 v6
AS41722 18 54
v4 v6
AS28910 19 51
v4 v6
AS49434 19 51
v4 v6
AS29049 19 50
v4
AS49673 TRUENETWORK 16 50
v4
AS13004 19 49
v4
AS35598 17 48
v4
AS51185 MAINSTREAMING-AS 17 48
v4
AS37721 ORG-VTS1-AFRINIC 17 47
v4
AS199524 GCORE 5 6
v4

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.