Skip to main content

AS212683

OLILO-AS

==========================================================

Registry

Authoritative registration data

AS number
212683
Name
OLILO-AS
Organisation
==========================================================
Country
—
RIR
RIPE
Registered
Source:asn:rdap retrieved

IPv4 prefixes

29

IPv6 prefixes

2

Total announced

31

Announced prefixes

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

Prefixes announced by AS212683
94.193.32.0/20 IPv4 /20 not checked
51.241.196.0/23 IPv4 /23 not checked
51.241.232.0/23 IPv4 /23 not checked
143.14.242.0/24 IPv4 /24 not checked
143.14.243.0/24 IPv4 /24 not checked
158.173.146.0/24 IPv4 /24 not checked
158.173.147.0/24 IPv4 /24 not checked
188.220.87.0/24 IPv4 /24 not checked
188.221.106.0/24 IPv4 /24 not checked
188.221.111.0/24 IPv4 /24 not checked
188.221.17.0/24 IPv4 /24 not checked
188.221.186.0/24 IPv4 /24 not checked
188.221.52.0/24 IPv4 /24 not checked
5.182.115.0/24 IPv4 /24 not checked
51.146.19.0/24 IPv4 /24 not checked
51.194.132.0/24 IPv4 /24 not checked
51.194.133.0/24 IPv4 /24 not checked
51.241.192.0/24 IPv4 /24 not checked
51.241.193.0/24 IPv4 /24 not checked
51.241.195.0/24 IPv4 /24 not checked
51.241.253.0/24 IPv4 /24 not checked
51.241.64.0/24 IPv4 /24 not checked
51.241.76.0/24 IPv4 /24 not checked
82.39.94.0/24 IPv4 /24 not checked
82.39.95.0/24 IPv4 /24 not checked
82.39.96.0/24 IPv4 /24 not checked
82.39.97.0/24 IPv4 /24 not checked
87.82.224.0/24 IPv4 /24 not checked
87.82.225.0/24 IPv4 /24 not checked
2a11:2646::/32 IPv6 /32 RPKI valid
2a11:2647::/32 IPv6 /32 RPKI valid

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 AS212683
Address families
LINX LON1: Main 4,000 Mbps IPv4 · IPv6
LINX LON2 4,000 Mbps IPv4 · IPv6
LONAP: LON0 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 AS212683 in BGP paths by route collectors.

Source:ripestat:asn-neighbours observed

Observed upstreams

45 networks seen before AS212683 in AS paths

No rows match “”.

Showing – of

Observed downstreams

19 networks seen after AS212683 in AS paths

Observed downstreams
Families
AS204776 Mintopia 401 857
v4 v6
AS205705 JDL-AS 264 684
v4 v6
AS213626 BIONIC-NETWORK 217 582
v6
AS199462 NETISP-UK-AS 451 571
v4 v6
AS48987 JYANGNET 406 570
v4 v6
AS213460 simplisticnodeus 385 570
v4 v6
AS205702 COMPLICITY 406 569
v4 v6
AS198375 DELUSION-NET 386 569
v4 v6
AS207155 STORMNET 382 559
v4 v6
AS218495 365 558
v6
AS209300 TWD2-NET 354 537
v4 v6
AS219380 ADNAANSIDDIQI 321 386
v4 v6
AS199686 aaroncarson 221 323
v6
AS218744 220 293
v6
AS199109 FruburyNet 218 293
v6
AS213210 kingslanding-as 217 292
v6
AS208755 NETWORKABLE 140 261
v4 v6
AS219280 ASTRONDO-AS 54 62
v4
AS208147 Snuggle 1 1
v4

No rows match “”.

Showing – of

Uncertain adjacencies

17 adjacencies that may be an artefact of collector peering

Uncertain adjacencies
Families
AS24482 SGGS-AS-AP 19 378
v4 v6
AS50300 CUSTDC 19 59
v4 v6
AS49544 i3Dnet 18 58
v4 v6
AS62167 Tismi 20 57
v4 v6
AS36236 NETACTUATE 18 57
v4 v6
AS61573 ASN61573 19 55
v4 v6
AS17639 CONVERGE-AS 18 53
v4 v6
AS48185 team_blue 13 41
v4 v6
AS34927 iFog-GmbH 12 40
v4 v6
AS198150 SIACOM-AS 12 40
v4 v6
AS16347 INHERENT 10 38
v4 v6
AS18106 VIEWQWEST-SG-AP 10 37
v4 v6
AS37721 ORG-VTS1-AFRINIC 9 36
v4 v6
AS263152 ASN263152 8 35
v4
AS13237 LAMBDANET-AS 7 34
v4
AS51185 MAINSTREAMING-AS 6 34
v4 v6
AS8529 OMANTEL-AS 16 20
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.