Skip to main content

AS60672

SC

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

Registry

Authoritative registration data

AS number
60672
Name
SC
Organisation
---------------------------------------------------
Country
—
RIR
RIPE
Registered
Source:asn:rdap retrieved

IPv4 prefixes

24

IPv6 prefixes

3

Total announced

27

Announced prefixes

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

Prefixes announced by AS60672
31.24.104.0/21 IPv4 /21 not checked
31.28.88.0/21 IPv4 /21 not checked
178.18.120.0/22 IPv4 /22 not checked
31.28.76.0/22 IPv4 /22 not checked
92.242.160.0/22 IPv4 /22 not checked
185.182.68.0/23 IPv4 /23 not checked
193.192.2.0/23 IPv4 /23 not checked
193.193.162.0/23 IPv4 /23 not checked
94.126.44.0/23 IPv4 /23 not checked
147.79.57.0/24 IPv4 /24 not checked
185.182.68.0/24 IPv4 /24 not checked
185.182.69.0/24 IPv4 /24 not checked
193.192.2.0/24 IPv4 /24 not checked
31.28.64.0/24 IPv4 /24 not checked
31.28.69.0/24 IPv4 /24 not checked
31.28.71.0/24 IPv4 /24 not checked
31.28.73.0/24 IPv4 /24 not checked
31.28.87.0/24 IPv4 /24 not checked
82.192.106.0/24 IPv4 /24 not checked
91.211.152.0/24 IPv4 /24 not checked
92.242.161.0/24 IPv4 /24 not checked
94.126.41.0/24 IPv4 /24 not checked
94.126.42.0/24 IPv4 /24 not checked
94.126.46.0/24 IPv4 /24 not checked
2a01:8000::/32 IPv6 /32 RPKI valid
2a10:6740::/32 IPv6 /32 RPKI valid
2a10:c883::/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 AS60672
Address families
LINX LON1: Main 10,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 AS60672 in BGP paths by route collectors.

Source:ripestat:asn-neighbours observed

Observed upstreams

3 networks seen before AS60672 in AS paths

Observed upstreams
Families
AS3356 LEVEL3 2,492 23,484
v4 v6
AS2914 NTT-DATA-2914 1,961 21,434
v4 v6
AS34309 LINK11 43 55
v4

No rows match “”.

Showing – of

Observed downstreams

14 networks seen after AS60672 in AS paths

Observed downstreams
Families
AS202656 XServerCloud 523 28,040
v4 v6
AS39150 HOSTING-TELECOM-AS 348 1,654
v4 v6
AS57148 TBSH-CLIENT-TRISTAR-BYTEHOUSE 356 1,652
v4
AS201862 VMhosts-London-AS 276 1,284
v4
AS219250 CIVO-LON2 413 660
v4
AS215089 FASTPANDA 263 660
v4
AS214056 FUTURETECH 261 660
v4
AS48611 CABLESTREET-AS 346 659
v4 v6
AS206357 ALDERMORE 259 414
v4
AS19797 SIMNET 260 330
v4
AS213513 COMPUTLE 260 330
v4
AS50489 ORIEDGE 259 329
v4
AS211552 CIVO-UK 34 140
v4 v6
AS212031 BITSolutions-AS 25 49
v4

No rows match “”.

Showing – of

Uncertain adjacencies

2 adjacencies that may be an artefact of collector peering

Uncertain adjacencies
Families
AS48185 team_blue 15 390
v4
AS39122 BLACKNIGHT-AS 15 140
v4 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.