Megabyte IKE is a Greek ISP operating AS210768 with 768 IPv4 addresses and three upstream providers. All evidence comes from RIPE registry and third-party ASN platforms; no corporate filings, website content, or named personnel are available. The profile serves as a registry-intelligence node for routing integrity monitoring. Any change in registry records, BGP announcements, or upstream relationships would alter the baseline. The entity should be treated as an organisation, not a person, despite database misclassification.
MEGABYTE-AS Megabyte IKE functions as a local Greek ISP and autonomous system number holder. Its public role is visible solely through RIPE NCC registry entries, BGP announcements, and ASN intelligence platforms. The organisation holds AS210768 with three IPv4 netblocks and depends on upstream transit from three external networks. There is no independent corporate website content, business registration, or personnel listing that would confirm its commercial operations or customer base.
Shifts in Megabyte IKE’s routing posture, registry records, or upstream dependencies could affect connectivity for 768 IPv4 addresses and alter abuse-handling pathways. For analysts mapping Greek network infrastructure or investigating routing anomalies, this operator represents an observable node. The absence of IPv6 and independent corporate data makes any registry change a significant signal for service continuity or expansion.
Shifts in Megabyte IKE’s routing posture, registry records, or upstream dependencies could affect connectivity for 768 IPv4 addresses and alter abuse-handling pathways. For analysts mapping Greek network infrastructure or investigating routing anomalies, this operator represents an observable node. The absence of IPv6 and independent corporate data makes any registry change a significant signal for service continuity or expansion.
MEGABYTE-AS Megabyte IKE functions as a local Greek ISP and autonomous system number holder. Its public role is visible solely through RIPE NCC registry entries, BGP announcements, and ASN intelligence platforms. The organisation holds AS210768 with three IPv4 netblocks and depends on upstream transit from three external networks. There is no independent corporate website content, business registration, or personnel listing that would confirm its commercial operations or customer base.
Changes to Megabyte IKE’s RPKI/IRR validation, BGP announcements, or registry contacts directly alter the reachability and attribution of its address space. A withdrawal or misconfiguration could disrupt service for its downstream customers, while new upstream relationships or IPv6 adoption would signal infrastructure evolution. For incident responders, its registry records offer a point of verification and a trigger for abuse-contact updates.
Megabyte IKE is a Greek ISP operating AS210768 with 768 IPv4 addresses and three upstream providers. All evidence comes from RIPE registry and third-party ASN platforms; no corporate filings, website content, or named personnel are available. The profile serves as a registry-intelligence node for routing integrity monitoring. Any change in registry records, BGP announcements, or upstream relationships would alter the baseline. The entity should be treated as an organisation, not a person, despite database misclassification.
Changes to Megabyte IKE’s RPKI/IRR validation, BGP announcements, or registry contacts directly alter the reachability and attribution of its address space. A withdrawal or misconfiguration could disrupt service for its downstream customers, while new upstream relationships or IPv6 adoption would signal infrastructure evolution. For incident responders, its registry records offer a point of verification and a trigger for abuse-contact updates.
| 0.90–1.00 | A | High — direct sources |
| 0.75–0.89 | A/B | Strong |
| 0.55–0.74 | B/C | Medium |
| 0.35–0.54 | C/D | Weak–medium |
| 0.10–0.34 | D | Weak signal |
| 0.00–0.09 | D | Internal monitoring |
Several public sources
MEGABYTE-AS Megabyte IKE
Megabyte IKE is a Greek Internet service provider operating autonomous system AS210768. It supplies fixed-line connectivity through 768 IPv4 addresses, relying on three upstream transit providers and no IPv6 capability. All evidence originates from RIPE NCC registry entries and routing intelligence platforms; no independent corporate records are available to confirm its business structure or customer base.
Why It Matters
Changes to Megabyte IKE’s RPKI/IRR validation, BGP announcements, or registry contacts directly alter the reachability and attribution of its address space. A withdrawal or misconfiguration could disrupt service for its downstream customers, while new upstream relationships or IPv6 adoption would signal infrastructure evolution. For incident responders, its registry records offer a point of verification and a trigger for abuse-contact updates.
What Public Sources Show
Megabyte IKE, operating autonomous system AS210768, is a small fixed-line Internet service provider in Greece. Public registries and routing platforms show it manages 768 IPv4 addresses across three prefixes and connects to three upstream providers. Its operations are documented only in RIPE NCC records and third-party ASN intelligence; no corporate filings or website content could be verified independently.
The ASN was allocated in September 2021 and relies on transit from Cogent Communications, Novelcomm LP, and VESTITEL BG. No downstream autonomous systems or peering partners appear in public routing data. All three IPv4 blocks originate from AS210768, and no IPv6 addresses are announced or assigned.
Changes in Megabyte IKE’s BGP announcements, registry contacts, or RPKI validation status directly affect the reachability and attribution of its address space. A misconfiguration or withdrawal could disrupt connectivity for its customer base. For network analysts, the operator serves as an observable node in Greek infrastructure mapping and routing anomaly detection.
Consistent records from RIPEstat, IPinfo, IPGeolocation, Cloudflare Radar, and IP2Location confirm its AS name, prefix set, and upstreams. RIPE WHOIS mirrors show organisation ID ORG-GABY1-RIPE and a role object labelled Megabyte Private Company. None of the sources provides downstream customer details or an independently verified corporate presence beyond the domain megabytenet.gr.
Its public control surface is limited to RIPE registry objects—aut-num, route objects, maintainer records—and BGP state for the three prefixes. No PeeringDB entry, additional ASNs, or IPv6 presence exists. Any shift in these records or upstream dependencies would alter the entire connectivity baseline for this single-homed operator.
Watch for RIPE record updates, new BGP announcements, or IPv6 allocation. The appearance of a corporate website, PeeringDB profile, or downstream customers would increase confidence in its operational posture. The composite name MEGABYTE-AS Megabyte IKE introduces ambiguity; the trading entity may differ. All assessments remain bounded by the limited registry evidence currently available.
Operating Surface
MEGABYTE-AS Megabyte IKE functions as a local Greek ISP and autonomous system number holder. Its public role is visible solely through RIPE NCC registry entries, BGP announcements, and ASN intelligence platforms. The organisation holds AS210768 with three IPv4 netblocks and depends on upstream transit from three external networks. There is no independent corporate website content, business registration, or personnel listing that would confirm its commercial operations or customer base.
Shifts in Megabyte IKE’s routing posture, registry records, or upstream dependencies could affect connectivity for 768 IPv4 addresses and alter abuse-handling pathways. For analysts mapping Greek network infrastructure or investigating routing anomalies, this operator represents an observable node. The absence of IPv6 and independent corporate data makes any registry change a significant signal for service continuity or expansion.
Watchpoints
The profile represents a baseline registry-intelligence node for a small Greek ISP. Its modest footprint and lack of independent verification make every registry or routing change a high-signal event. Monitoring should focus on record hygiene and any evidence of commercial operation beyond RIPE entries.
Concrete watchpoints include RIPE aut-num modification, new prefix announcements, IPv6 adoption, appearance of a PeeringDB profile, changes in upstream peer set, and publication of a corporate website. Any of these would justify updating the profile from registry-only to operator-confirmed status.
No Greek commercial registry check was performed; corporate address, legal form, and director names are missing. The domain megabytenet.gr was not crawled for content. Personnel names are absent from RIPE role objects. BGP data was not sampled directly; all routing claims rely on third-party platform snapshots.
Sources
- Internet registry record - public-source identity and registry context for MEGABYTE-AS Megabyte IKE.
- ipinfo.io - Lists AS210768 as Megabyte IKE in Greece, website megabytenet.gr, ASN type ISP, RIPE registry, 768 IPv4 addresses, zero IPv6 addresses, allocation date 2021-09-10, update date 2025-05-24, three IPv4 ranges, peers/upstreams, and no downstreams.
- radar.cloudflare.com - Identifies AS210768 as MEGABYTE-AS in Greece and presents routing statistics, announced prefix views, connectivity views, and estimated AS customer population measurements.
- ipgeolocation.io - Lists AS210768 as MEGABYTE-AS, organisation Megabyte IKE, country GR, website megabytenet.gr, three IPv4 routes, zero IPv6 routes, RIPE registry, assigned status, allocation date 2021-09-10, peers, upstreams, and RIPE-derived WHOIS role context.
- lite.ip2location.com - Lists AS210768 Megabyte Ike in Greece, domain megabytenet.gr, fixed line ISP classification, 768 IPv4 addresses, zero IPv6 addresses, and the same three IPv4 netblocks.
- ipinfo.io - Shows 93.170.191.0/24 as a RIPE-sourced MEGABYTE-NET range for AS210768/Megabyte IKE, with route origin AS210768 and RIPE-derived organisation and role records.
- ipinfo.io - Shows the 95.46.36.0/24 and 95.46.37.0/24 public range context under MEGABYTE-NET, RIPE registry, organisation ORG-GABY1-RIPE, and route origin AS210768 via the parent route 95.46.36.0/23.
- Registry RDAP / WHOIS record - Mirrors RIPE WHOIS details for AS210768, including AS name MEGABYTE-AS, organisation Megabyte IKE, country Greece, RIPE registry, three IPv4 prefixes, imported and exported routing policy lines, and RIPE role object context.
Domain of operation
Megabyte IKE is a Greek Internet service provider operating autonomous system AS210768. It supplies fixed-line connectivity through 768 IPv4 addresses, relying on three upstream transit providers and no IPv6 capability. All evidence originates from RIPE NCC registry entries and routing intelligence platforms; no independent corporate records are available to confirm its business structure or customer base.
- Internet registry record: public-source identity and registry context for MEGABYTE-AS Megabyte IKE. Evidence basis: source-3a5dd3cfe075
Timeline
- MEGABYTE-AS Megabyte IKE public evidence observed
Shifts in Megabyte IKE’s routing posture, registry records, or upstream dependencies could affect connectivity for 768 IPv4 addresses and alter abuse-handling pathways. For analysts mapping Greek network infrastructure or investigating routing anomalies, this operator represents an observable node. The absence of IPv6 and independent corporate data makes any registry change a significant signal for service continuity or expansion.
At A Glance
- Name: MEGABYTE-AS Megabyte IKE
- Type: Individual registry-holder label
- Base: Greece
- Profile focus: Institution
What It Does
- public operating records
- official service pages
- source-backed relationship updates
Why It Matters
- Changes to Megabyte IKE’s RPKI/IRR validation, BGP announcements, or registry contacts directly alter the reachability and attribution of its address space. A withdrawal or misconfiguration could disrupt service for its downstream customers, while new upstream relationships or IPv6 adoption would signal infrastructure evolution. For incident responders, its registry records offer a point of verification and a trigger for abuse-contact updates.
- Operational criticality: Medium
- Time horizon: Next quarter
What To Watch
- official company sources
- public registries
- operator-published records
Track verified source updates, role changes, and current public evidence.
Changes to Megabyte IKE’s RPKI/IRR validation, BGP announcements, or registry contacts directly alter the reachability and attribution of its address space. A withdrawal or misconfiguration could disrupt service for its downstream customers, while new upstream relationships or IPv6 adoption would signal infrastructure evolution. For incident responders, its registry records offer a point of verification and a trigger for abuse-contact updates.
Longer-term relevance depends on verified operating, policy, and relationship changes.
Member Briefing
Deeper Profile Context
Login is required to unlock the full profile briefing and source notes.
Only for Strategy Circle
Strategic Circle Access
Open to all readers. Unlock profile briefings after joining and logging in.
Join Strategic CircleOnly for Leadership Alliance
Leadership Alliance Access
For owners and management of IP-holding companies. Login required to unlock.
Join Leadership AlliancePublic View
Changes to Megabyte IKE’s RPKI/IRR validation, BGP announcements, or registry contacts directly alter the reachability and attribution of its address space. A withdrawal or misconfiguration could disrupt service for its downstream customers, while new upstream relationships or IPv6 adoption would signal infrastructure evolution. For incident responders, its registry records offer a point of verification and a trigger for abuse-contact updates.
Watchpoints
- The profile represents a baseline registry-intelligence node for a small Greek ISP.
- Its modest footprint and lack of independent verification make every registry or routing change a high-signal event.
- Monitoring should focus on record hygiene and any evidence of commercial operation beyond RIPE entries.
Caveats
- Public evidence is used only for source-backed claims.
- Private control or contract claims require separate public support.
FAQ
Why does BTW track MEGABYTE-AS Megabyte IKE?
Shifts in Megabyte IKE’s routing posture, registry records, or upstream dependencies could affect connectivity for 768 IPv4 addresses and alter abuse-handling pathways. For analysts mapping Greek network infrastructure or investigating routing anomalies, this operator represents an observable node. The absence of IPv6 and independent corporate data makes any registry change a significant signal for service continuity or expansion.
What evidence supports the profile?
public-source identity and registry context for MEGABYTE-AS Megabyte IKE.
What should readers watch next?
The profile represents a baseline registry-intelligence node for a small Greek ISP.






