Skip to main content

AS16082

SPITFIRE

[email protected]

Registry

Authoritative registration data

AS number
16082
Name
SPITFIRE
Organisation
[email protected]
Country
RIR
RIPE
Registered
Source:asn:rdap retrieved

IPv4 prefixes

12

IPv6 prefixes

1

Total announced

13

Announced prefixes

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

Prefixes announced by AS16082
87.224.0.0/17 IPv4 /17 not checked
212.237.64.0/19 IPv4 /19 not checked
217.13.128.0/19 IPv4 /19 not checked
62.133.0.0/19 IPv4 /19 not checked
83.218.128.0/19 IPv4 /19 not checked
109.238.64.0/20 IPv4 /20 not checked
31.24.0.0/21 IPv4 /21 not checked
37.77.176.0/21 IPv4 /21 not checked
87.117.112.0/21 IPv4 /21 not checked
87.117.72.0/21 IPv4 /21 not checked
185.15.104.0/22 IPv4 /22 not checked
193.36.128.0/22 IPv4 /22 not checked
2a02:b90::/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 AS16082
Address families
LINX LON1: Main 100,000 Mbps IPv4 · IPv6
LINX LON2 100,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 AS16082 in BGP paths by route collectors.

Source:ripestat:asn-neighbours observed

Observed upstreams

47 networks seen before AS16082 in AS paths

Observed upstreams
Families
AS174 COGENT-174 138 1,081
v4 v6
AS3356 LEVEL3 111 932
v4 v6
AS6939 HURRICANE 193 397
v4 v6
AS9002 RETN-AS 25 259
v4 v6
AS6461 ZAYO-6461 11 217
v4 v6
AS13030 INIT7 18 159
v4 v6
AS25091 IP-Max 13 145
v4 v6
AS34549 MEER-AS 11 98
v4 v6
AS33891 CORE-BACKBONE 10 98
v4
AS35280 F5 9 70
v4 v6
AS14840 ASN14840 4 70
v4
AS5405 8 59
v4 v6
AS3214 XTOM 4 58
v4 v6
AS48362 TKSWF-AS 4 56
v4 v6
AS50304 6 42
v4
AS34927 iFog-GmbH 4 42
v4
AS29075 6 32
v4 v6
AS6057 6057 4 30
v4 v6
AS8455 4 30
v4 v6
AS34177 CELESTE-AS 4 29
v4 v6
AS41327 FIBERTELECOM-AS 4 29
v4 v6
AS37497 ORG-NPL3-AFRINIC 4 28
v4
AS39351 ESAB-AS 4 28
v4
AS9044 2 28
v4
AS12552 2 28
v4
AS1267 3 26
v4
AS20562 3 26
v4
AS37468 ORG-AC4-AFRINIC 2 22
v4
AS60171 2 15
v4 v6
AS3216 SOVAM-AS 2 14
v4
AS3741 2 14
v4
AS4455 2 14
v4
AS4637 ASN-TELSTRA-GLOBAL 2 14
v4
AS6204 2 14
v4
AS6663 2 14
v4
AS7195 7195 2 14
v4
AS7575 2 14
v4
AS8220 COLT 2 14
v4
AS15802 DU-AS1 2 14
v4
AS21215 2 14
v4
AS29169 GANDI-AS 2 14
v4
AS37100 2 14
v4
AS37282 2 14
v4
AS137409 GSLNETWORKS-AS-AP 2 14
v4
AS215638 AS-CILIX-LIMITED 2 14
v4
AS15412 FLAG-AS 1 1
v4
AS64496 1 1
v4

No rows match “”.

Showing of

Observed downstreams

1 networks seen after AS16082 in AS paths

Observed downstreams
Families
AS61093 263 682
v4

No rows match “”.

Showing of

Uncertain adjacencies

38 adjacencies that may be an artefact of collector peering

Uncertain adjacencies
Families
AS24482 SGGS-AS-AP 2 163
v4 v6
AS12779 ITGATE 2 60
v4 v6
AS48185 2 45
v4 v6
AS25160 2 30
v4 v6
AS49544 i3Dnet 2 30
v4 v6
AS51185 MAINSTREAMING-AS 2 30
v4 v6
AS62167 2 30
v4 v6
AS212483 level86 2 28
v4
AS1828 UNITAS 2 15
v4 v6
AS3170 2 15
v4 v6
AS6424 2 15
v4 v6
AS14630 INVESCO 2 15
v4 v6
AS16347 2 15
v4 v6
AS31742 SOTACONNECT 2 15
v4 v6
AS34288 2 15
v4 v6
AS36236 NETACTUATE 2 15
v4 v6
AS39122 2 15
v4 v6
AS42473 2 15
v4 v6
AS48070 2 15
v4 v6
AS50300 2 15
v4 v6
AS61573 2 15
v4 v6
AS6894 2 14
v4
AS8426 CLARANET-AS 2 14
v4
AS12969 2 14
v4
AS13237 LAMBDANET-AS 2 14
v4
AS17639 CONVERGE-AS 2 14
v4
AS18106 VIEWQWEST-SG-AP 2 14
v4
AS28792 2 14
v4
AS35266 2 14
v4
AS37680 2 14
v4
AS37721 ORG-VTS1-AFRINIC 2 14
v4
AS198150 SIACOM-AS 2 14
v4
AS207841 2 14
v4
AS263152 2 14
v4
AS271253 2 14
v4
AS8529 OMANTEL-AS 1 2
v6
AS31122 DIGIWEB-AS 1 1
v6
AS213241 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.