Skip to main content

AS203012

gestioniza

FIBRITEL TELECOMUNICACIONES SL

Registry

Authoritative registration data

AS number
203012
Name
gestioniza
Organisation
FIBRITEL TELECOMUNICACIONES SL
Country
—
RIR
RIPE
Registered
Source:asn:rdap retrieved

IPv4 prefixes

1

IPv6 prefixes

0

Total announced

1

Announced prefixes

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

Prefixes announced by AS203012
43.230.184.0/24 IPv4 /24 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 AS203012 in BGP paths by route collectors.

Source:ripestat:asn-neighbours observed

Observed upstreams

9 networks seen before AS203012 in AS paths

Observed upstreams
Families
AS199081 LANCOM 172 215
v4
AS6939 HURRICANE 30 33
v4
AS174 COGENT-174 7 7
v4
AS6762 SEABONE-NET 4 6
v4
AS22356 ASN22356 5 5
v4
AS14840 ASN14840 2 5
v4
AS50877 AIRBEAM-AS 2 2
v4
AS8280 SYNAPSECOM-AS 1 1
v4
AS9498 BBIL-AP 1 1
v4

No rows match “”.

Showing – of

Observed downstreams

0 networks seen after AS203012 in AS paths

No downstreams observed

This AS was not seen carrying traffic towards another network.

Uncertain adjacencies

4 adjacencies that may be an artefact of collector peering

Uncertain adjacencies
Families
AS51185 MAINSTREAMING-AS 1 1
v4
AS56457 FASTPATH 1 1
v4
AS197580 AS-CONNECTICORE 1 1
v4
AS198150 SIACOM-AS 1 1
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.