Skip to main content

AS8896

XFIBER-AS

----

Registry

Authoritative registration data

AS number
8896
Name
XFIBER-AS
Organisation
----
Country
RIR
RIPE
Registered
Source:asn:rdap retrieved

IPv4 prefixes

19

IPv6 prefixes

7

Total announced

26

Announced prefixes

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

Prefixes announced by AS8896
212.33.128.0/19 IPv4 /19 not checked
77.241.96.0/20 IPv4 /20 not checked
81.29.32.0/20 IPv4 /20 not checked
89.221.96.0/20 IPv4 /20 not checked
185.126.184.0/22 IPv4 /22 not checked
185.15.216.0/22 IPv4 /22 not checked
185.92.52.0/22 IPv4 /22 not checked
45.138.236.0/22 IPv4 /22 not checked
91.188.232.0/22 IPv4 /22 not checked
185.15.216.0/24 IPv4 /24 not checked
185.152.33.0/24 IPv4 /24 not checked
185.156.112.0/24 IPv4 /24 not checked
185.156.114.0/24 IPv4 /24 not checked
185.41.241.0/24 IPv4 /24 not checked
45.138.238.0/24 IPv4 /24 not checked
45.138.239.0/24 IPv4 /24 not checked
45.90.36.0/24 IPv4 /24 not checked
45.90.37.0/24 IPv4 /24 not checked
89.254.20.0/24 IPv4 /24 not checked
2a00:1e18::/29 IPv6 /29 not checked
2a03:9a00::/29 IPv6 /29 not checked
2a00:1e18::/32 IPv6 /32 not checked
2a00:1e19::/32 IPv6 /32 not checked
2a03:9a00::/32 IPv6 /32 not checked
2a09:a300::/32 IPv6 /32 not checked
2a10:1b81::/32 IPv6 /32 not checked

No rows match “”.

Showing of

Source:ripestat:announced-prefixes observed

Observed adjacencies

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

Source:ripestat:asn-neighbours observed

Observed upstreams

7 networks seen before AS8896 in AS paths

Observed upstreams
Families
AS12552 2,280 9,776
v4 v6
AS1299 1,291 4,717
v4 v6
AS6453 80 98
v4
AS50304 17 37
v4
AS2116 11 13
v6
AS56655 6 7
v4
AS29695 1 1
v4

No rows match “”.

Showing of

Observed downstreams

43 networks seen after AS8896 in AS paths

Observed downstreams
Families
AS2116 2,050 8,714
v4 v6
AS12552 632 7,329
v4 v6
AS33891 1,328 6,910
v4 v6
AS13335 893 5,694
v4
AS16509 58 3,654
v4 v6
AS212642 353 746
v4 v6
AS2603 213 730
v4 v6
AS50229 267 696
v4
AS201888 338 692
v4 v6
AS3399 92 548
v4 v6
AS197519 254 515
v4 v6
AS4913 368 494
v4
AS1299 14 466
v4 v6
AS28824 92 372
v4 v6
AS201454 59 360
v4 v6
AS22717 265 347
v4
AS205238 263 345
v4
AS202174 262 344
v4
AS213148 262 344
v4
AS72 259 343
v4
AS41049 107 288
v4
AS2119 39 210
v4 v6
AS25400 25 205
v4 v6
AS29695 28 115
v4 v6
AS6667 39 105
v4
AS48680 76 88
v4
AS34087 23 72
v4 v6
AS15659 3 17
v4 v6
AS56655 4 15
v4 v6
AS25148 3 14
v4
AS203779 3 13
v4 v6
AS39783 1 12
v4 v6
AS19679 1 9
v4 v6
AS200781 2 5
v4 v6
AS702 1 5
v4
AS31726 1 5
v4
AS224 2 4
v4
AS21293 1 3
v4
AS26415 1 3
v4 v6
AS6453 1 1
v4
AS41741 1 1
v4
AS49544 1 1
v6
AS49788 1 1
v4

No rows match “”.

Showing of

Uncertain adjacencies

6 adjacencies that may be an artefact of collector peering

Uncertain adjacencies
Families
AS28824 5,463 34,889
v4 v6
AS24482 7 117
v4 v6
AS49544 13 82
v4 v6
AS3399 13 43
v4 v6
AS34927 7 36
v4 v6
AS57381 7 36
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.