Skip to main content

AS35313

BH-INFONAS-ASN

ORG-IW13-RIPE

Registry

Authoritative registration data

AS number
35313
Name
BH-INFONAS-ASN
Organisation
ORG-IW13-RIPE
Country
—
RIR
RIPE
Registered
Source:asn:rdap retrieved

IPv4 prefixes

7

IPv6 prefixes

0

Total announced

7

Announced prefixes

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

Prefixes announced by AS35313
80.88.240.0/20 IPv4 /20 not checked
188.137.128.0/21 IPv4 /21 not checked
188.137.136.0/21 IPv4 /21 not checked
188.137.144.0/21 IPv4 /21 not checked
80.88.240.0/21 IPv4 /21 not checked
80.88.248.0/21 IPv4 /21 not checked
188.137.140.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

Internet Exchange memberships listed for AS35313
Address families
DE-CIX Frankfurt: DE-CIX Frankfurt Peering LAN 1,000 Mbps IPv4 · IPv6
DE-CIX New York: DE-CIX New York Peering LAN 1,000 Mbps IPv4 · IPv6
LINX LON1: Main 1,000 Mbps IPv4 · IPv6
LONAP: LON0 1,000 Mbps IPv4 · IPv6
SH-IX 1,000 Mbps IPv4 · IPv6
UAE-IX: UAE-IX Peering LAN 1,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 AS35313 in BGP paths by route collectors.

Source:ripestat:asn-neighbours observed

Observed upstreams

27 networks seen before AS35313 in AS paths

No rows match “”.

Showing – of

Observed downstreams

3 networks seen after AS35313 in AS paths

Observed downstreams
Families
AS42909 COMMUNITYDNS 66 162
v4
AS8674 NETNOD-IX 25 71
v4 v6
AS210968 SINNAD-BAH 19 24
v4

No rows match “”.

Showing – of

Uncertain adjacencies

73 adjacencies that may be an artefact of collector peering

Uncertain adjacencies
Families
AS24482 SGGS-AS-AP 2 36
v4
AS47147 AS-ANX 2 32
v4
AS12779 ITGATE 2 30
v4
AS14840 ASN14840 1 24
v4
AS25091 IP-Max 1 18
v4
AS48185 team_blue 1 18
v4
AS35710 WEBERCLOUD 2 16
v4
AS62167 Tismi 2 16
v4
AS25160 VORBOSS 2 14
v4
AS49544 i3Dnet 2 14
v4
AS8674 NETNOD-IX 2 12
v4 v6
AS3214 XTOM 1 12
v4
AS15547 NETPLUS 1 12
v4
AS47692 NESSUS 1 12
v4
AS51184 FONIRA 1 12
v4
AS51185 MAINSTREAMING-AS 1 12
v4
AS199524 GCORE 1 12
v4
AS553 BELWUE 3 9
v4
AS917 MISAKA 3 9
v4
AS35360 GARGUNET 3 9
v4
AS37680 ORG-CIc1-AFRINIC 3 9
v4
AS57187 DATAMENA-ASN 3 9
v4
AS271253 ASN271253 3 9
v4
AS835 GOCODEIT-EDGE 2 8
v4
AS1828 UNITAS 2 8
v4
AS5405 INTERDOTLINK 2 8
v4
AS6424 EDGOO 2 8
v4
AS8298 IPNG 2 8
v4
AS14630 INVESCO 2 8
v4
AS20932 SIG-ST 2 8
v4
AS22652 FIBRENOIRE-INTERNET 2 8
v4
AS25220 GLOBALNOC-AS 2 8
v4
AS28792 PUBLIC-INTERNET 2 8
v4
AS29140 HOSTSERVER-AS 2 8
v4
AS29691 NINE 2 8
v4
AS31510 IKB-AS 2 8
v4
AS35266 EXN-AS 2 8
v4
AS42473 AS-ANEXIA 2 8
v4
AS42541 FIBERBY 2 8
v4
AS48070 DSM 2 8
v4
AS48919 UA-CITY-AS 2 8
v4
AS50300 CUSTDC 2 8
v4
AS50304 BLIX 2 8
v4
AS58057 SECUREBIT 2 8
v4
AS58299 OPENFACTORY-AS 2 8
v4
AS64475 FREIFUNK-FRANKFURT 2 8
v4
AS142271 DOUBLESQUARE-AS-AP 2 8
v4
AS199938 NETZWERGE 2 8
v4
AS205112 PHILUNET 2 8
v4
AS206356 Freifunk-Essen 2 8
v4
AS264479 ASN264479 2 8
v4
AS42909 COMMUNITYDNS 1 8
v4
AS210937 Showfom 2 7
v4
AS3212 TELEMACH 1 6
v4
AS13237 LAMBDANET-AS 1 6
v4
AS16347 INHERENT 1 6
v4
AS17639 CONVERGE-AS 1 6
v4
AS21412 CGATES-AS 1 6
v4
AS34177 CELESTE-AS 1 6
v4
AS35598 INETCOM 1 6
v4
AS36236 NETACTUATE 1 6
v4
AS37721 ORG-VTS1-AFRINIC 1 6
v4
AS39122 BLACKNIGHT-AS 1 6
v4
AS41327 FIBERTELECOM-AS 1 6
v4
AS44901 belcloud 1 6
v4
AS56987 AS-ABACLOUDA 1 6
v4
AS209823 ENKI-AS 1 6
v4
AS210968 SINNAD-BAH 1 4
v4
AS200612 GulfBridgeInternational 2 3
v4
AS8529 OMANTEL-AS 1 2
v4
AS8888 XTOM 1 2
v4
AS212483 level86 1 2
v4
AS6894 KDDI-EUROPE 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.