Ibroadband Internet Service makes a local connectivity bill depend on upstream routes and field repair

Summary

• Ibroadband Internet Service is not just a stray ASN label. Its own website advertises affordable broadband for home and corporate users in Mumbai, gives a Kurla West address and phone line, lists packages from 5Mbps to 100Mbps, and links to a customer payment portal whose terms say the service is operating only in Mumbai.
• The number-resource evidence is real but awkward. APNIC assigns AS141245, IBBNET-AS-IN, and the IPv4 block 103.157.178.0/23 to Ibroadband Internet Service at a shop address on A.H. Wadia Marg in Kurla West. On the routing table, however, RIPEstat shows AS141245 not announced, while the /23 is announced by AS138296, Juweriyah Networks Private Limited.
• The route-origin picture is not a simple hijack claim. RIPEstat's RPKI validation marks AS138296 valid for the /23, and a separate check for AS141245 also sees authorisation for Ibroadband's ASN. The operational point is that the visible route currently reaches the internet through Juweriyah, not through Ibroadband's dormant public ASN.
• The licensing and subscriber evidence is weaker than the service website. India's DoT internet-service authorisation portal and the 2026 ISP authorisation list are useful for understanding Category A, B and C territory, but the public files reviewed here do not identify an Ibroadband Internet Service licence row by that trading name. They do show other Kurla West operator records, so the exact licence holder and access-provider boundary need direct confirmation.
• The downgrade is therefore explicit: Ibroadband is a Mumbai broadband provider with a public customer surface and registered number resources, but public evidence does not verify its current subscriber count, fibre route, pole or duct rights, tower use, upstream contract, field staff, spares, backup-power duration, congestion profile or restoration performance. A local customer bill can still be real, but the resilience case depends on facts not visible in public sources.

A Mumbai broadband offer, not a proved regional network

The first fact to keep is that Ibroadband Internet Service presents itself as a provider, not as a passive company shell. Its homepage says iBroadband is an affordable internet broadband provider for home users and corporate customers in Mumbai. The same page gives contact information: two phone numbers, 932 339 3399 and 02225033399; an email address, [email protected]; and a shop address at A.H. Wadia Marg near Habib Hospital, Kurla West, Mumbai 400070. The text is old-fashioned, and the static page carries a 2018-era feel, but it is still reachable and still points users to a payment surface.

That payment surface matters. The site's Pay Now link opens a customer-login page asking for a username, mobile number or account ID. Its terms describe Ibroadband Internet Service as an organisation providing affordable broadband to home users and corporates, say it operates currently only in Mumbai, and say it delivers service through selected entrepreneurs who follow company standards. The same text claims thousands of clients trust the company with business-critical needs. That is a first-party claim, not an independently audited subscriber count, but it is more operational than a parked domain or a one-line business listing.

The public offer is also specific enough to describe a product envelope. The package page lists monthly plans from 5Mbps at INR500 to 100Mbps at INR2,500, with three-month, six-month and twelve-month prices and a note that GST applies. The contact page repeats the Kurla West address and identifies the legal name behind the page as Mohammed Ataul Mustafa Khan. The domain record for ibroadband.co.in shows the name registered in 2018, with expiration in 2028, and a registrant organisation string of "ibroadband internet service" in Maharashtra. The domain therefore does not look like a dead sales relic in the way a lapsed site would.

Those facts justify keeping Ibroadband in a regional-ISP economics frame, but they do not justify inflating it. The website does not publish a coverage map, a building list, a serviceable-address checker, an optical-line-terminal location, a tower list, a backhaul route, a peering policy, a network diagram, audited accounts or a regulator-reported subscriber count. It uses the language of city service, not the language of a measured regional carrier.

A realistic assessment has to sit between two errors: dismissing the company because its public routing is not self-originated, and overstating the network because a public-facing site says "Mumbai" and "thousands of clients."

The best description is evidence-bound. Ibroadband has a Mumbai retail surface, a payment path for existing users, public contact details, public package pricing and APNIC resources. What is missing is the proof that those pieces sit on top of a self-operated fibre or fixed-wireless network with identifiable redundancy. In small-access economics, that missing layer is the difference between a provider that owns enough physical plant to control repair and a provider whose customer service depends on other owners' ducts, poles, upstream routers and field teams.

That distinction is not pedantry. For a household, a small office or a local shop, the brand on the bill is the party expected to answer the phone when service fails. If Ibroadband controls the drop cable, the distribution node, the upstream handoff and the field crew, it can diagnose faults directly. If one or more of those layers belongs to a partner, landlord, cable operator or neighbouring ISP, the customer experience still belongs to Ibroadband but the recovery path is shared. The public record points to exactly that kind of boundary problem.

The number resources are real, but the autonomous system is idle

APNIC records give Ibroadband a clear network identity. The AS141245 RDAP record names IBBNET-AS-IN and describes the holder as Ibroadband Internet Service in India. It was registered on 22 October 2020 and last changed in September 2025. Its administrative and technical contact is a manager-admin role at shop no. 8, A.H. Wadia Marg, near Habib Hospital, Kurla West, with the same 02225033399 phone number seen on the public website and a [email protected] contact. APNIC's separate entity record for Mustafa Khan gives the same shop address, phone number and Ibroadband-domain email.

The IPv4 allocation is also specific. APNIC assigns 103.157.178.0/23, 512 IPv4 addresses from 103.157.178.0 through 103.157.179.255, to IBBNET, with the description Ibroadband Internet Service. The record is marked allocated portable and active, with a registration date in October 2020 and a last-changed date in August 2025. In practical terms, the company has the raw ingredients for an independent internet edge: an ASN and its own portable address block.

The routing state does not show that edge in use. RIPEstat's AS overview for AS141245 reports the ASN as not announced at the 10 July 2026 query snapshot. Its announced-prefixes result returns no current prefixes, and its routing-status result shows zero IPv4 space, zero IPv6 space, zero route-collector visibility and zero observed neighbours. RIPEstat's BGP state output likewise returns no active routes. CIDR Report's public summary for AS141245 says IBBNET-AS-IN - Ibroadband Internet Service, IN is not announced.

That does not mean the address space is unreachable. RIPEstat's prefix overview for 103.157.178.0/23 shows the prefix announced by AS138296, with the holder string STARNET7-AS - Juweriyah Networks Private Limited. Its routing history shows long visibility for the two /24 components and later the aggregate /23 through AS138296. APNIC's AS138296 record identifies Juweriyah Networks Private Limited, also in Kurla West, with the same 02225033399 phone number but different contact email and address detail.

The route-origin authorisation picture makes the boundary even more subtle. For 103.157.178.0/23 originated by AS138296, RIPEstat reports a valid status under a route-origin authorisation for AS138296. A check for 103.157.178.0/24 and AS141245 also reports valid authorisation for Ibroadband's ASN. So the issue is not that the visible Juweriyah route must be illegitimate. The issue is that the public control plane has an unused Ibroadband ASN and a visible Juweriyah origin for Ibroadband-numbered space.

For customers, that difference matters less than it does for engineers until something breaks. If Juweriyah originates Ibroadband's address space because it is the upstream, managed-router operator, affiliated network, reseller platform or shared local infrastructure provider, traffic may work perfectly well in normal conditions. But when a route is withdrawn, filtered, de-preferenced or congested, the public record does not show an Ibroadband-originated alternative path. It also does not show a second upstream, a route server presence, a public peering policy or a visible maintenance notice explaining the arrangement.

PeeringDB reinforces the asymmetry. A PeeringDB query for AS141245 returns no network entity, which is not proof of no peering because participation is voluntary. A PeeringDB query for AS138296, by contrast, returns Juweriyah Networks as a Cable/DSL/ISP with IPv4 and IPv6 prefix counts, 300-500Gbps traffic, four IX counts and two facilities. Those are Juweriyah's self-reported interconnection details, not Ibroadband's. They are useful because they show the visible origin ASN is not a trivial one-line entity. They are not evidence that Ibroadband itself has those exchange points or that its customer traffic enjoys every Juweriyah path.

The safe operating conclusion is therefore narrow. Ibroadband has its own ASN and address space. Its ASN is not visible in global BGP. Its address space is visible through Juweriyah Networks. Both origin paths appear to have route-origin authorisation. That is consistent with a local access provider relying on a related or upstream network for public routing. It is not enough to call Ibroadband independently multi-homed.

The legal and licence boundary needs confirmation

The legal surface is less clean than the number-resource surface. The website's contact page identifies the legal name as Mohammed Ataul Mustafa Khan. APNIC's Ibroadband records identify Mustafa Khan and manager-admin contacts at a nearby A.H. Wadia Marg shop address. The domain RDAP record identifies the registrant organisation as Ibroadband Internet Service in Maharashtra. These records align around the brand, address cluster and published contact points.

India's telecom authorisation system, however, uses licence holders and service areas, not just trading names. The DoT internet-service page explains that internet-service authorisations sit under Category A, B and C scopes. The Unified Licence agreement defines the territory structure and permits internet access through fibre, radio, underground copper, authorised cable networks, leased bandwidth and shared infrastructure under the relevant licence conditions. A licence row can therefore be held by a private company, and the customer-facing brand can still appear differently.

That is why the DoT lists are useful but not conclusive for Ibroadband. The 2026 ISP authorisation list and the earlier January 2025 list show the density of local ISP authorisations around Mumbai, including Kurla West records for Juweriyah Networks Private Limited. They do not, in the public text reviewed here, establish a separate Ibroadband Internet Service row by that exact trading name. That gap should not be overread. A service can be sold under a brand while the authorisation is held by another legal entity or proprietor, but that is precisely the point that needs confirmation before a strong operating profile is written.

The public-route evidence and the DoT evidence point in the same direction: the boundary between Ibroadband as a retail-facing brand and Juweriyah as a visible network operator cannot be ignored. AS138296 is the current public origin for Ibroadband-numbered space. Juweriyah appears in DoT authorisation lists and in PeeringDB. Ibroadband appears on its own website, domain registration and APNIC allocation. A responsible assessment does not collapse those identities into one company, nor does it invent a formal relationship that the public sources do not state.

The safer statement is what can be seen: there is a shared local contact environment, overlapping phone information, route-origin dependence and unresolved operating responsibility.

This is where a local connectivity bill becomes infrastructure evidence. The customer may know the brand, the login page and the technician who arrives. The internet may see AS138296. APNIC may see Ibroadband-numbered addresses. DoT may see a licence holder by another legal name. Each surface can be true at once, but they assign responsibility differently. The bill is resilient only if those responsibility lines are clear when a customer drop fails, an upstream handoff goes down, a payment record is disputed or a regulator asks who controls the service.

The recommended evidence to settle the question is concrete: a current DoT authorisation identifier tied to Ibroadband's operating name or proprietor, a current terms page identifying the licence holder, customer invoices showing the legal issuer, a maintenance notice naming the network operator, or an official service agreement between the retail brand and the AS138296 operator. None of that has to be public for service to be legal or real. It does have to be known before outside readers should treat Ibroadband as a standalone regional ISP.

The access plant is the part the public record does not show

The website says broadband. The package page says 5Mbps, 10Mbps, 16Mbps, 20Mbps, 25Mbps, 50Mbps and 100Mbps. The homepage says home users and corporate customers in Mumbai. The payment portal says service is delivered through selected entrepreneurs and that the company operates only in Mumbai. Those statements tell us the product posture. They do not identify the physical medium.

A small Mumbai access network could be built several ways. It might use fibre drops from a local cabinet into buildings. It might use Ethernet over building risers. It might lease an existing cable network. It might use wireless links for a short hop and fibre for backhaul. It might aggregate customers behind Juweriyah equipment while Ibroadband handles retail billing and field contact. It might combine all of those structures street by street. The public pages do not publish technology per address, so the assessment should not pick one design as fact.

This uncertainty matters because each design fails differently. A fibre drop can be cut at a building entry, damaged during road work or disconnected at a distribution box. A wireless hop can fade, lose alignment, suffer interference or fail with rooftop power. A cable-network arrangement can concentrate many customers behind one amplifier, splitter or local power point. A managed upstream handoff can leave the retail provider waiting on another operator's change window. Customers experience all of those as "the internet is down," but restoration depends on which layer failed.

India's infrastructure-protection tools show why that local layer is difficult. The DoT Call Before u Dig system exists to coordinate excavators and underground asset owners so damage can be reduced before digging starts. The Telecommunications Right of Way Rules, 2024 set procedures for underground and overground network permissions, notices and restoration costs. These rules are national, not Ibroadband-specific, but they describe the operating environment for any small provider that must place, protect or repair telecom assets in streets and buildings.

For a large carrier, one cut may be absorbed by a ring, a second feeder, a different duct or spare capacity through another exchange. For a small provider, the same cut can be the only customer path. The public Ibroadband record does not identify a ring, a redundant handoff, diverse poles, diverse ducts, protected conduit, route maps, wayleave arrangements or repair stock. If a customer building is fed by one cable route, one building switch and one upstream handoff, then the entire service promise depends on finding the fault, getting physical access and having the right spare parts quickly.

The website's selected-entrepreneur language is important here. It suggests a local field arrangement rather than a purely centralised carrier operation. That can be a strength. A local entrepreneur may know the buildings, security guards, roof access, cable paths and recurring fault points better than a remote call centre. It can also be a fragility. If the same person sells, collects, installs and repairs, then absence, illness, conflict with a building manager or lack of a replacement optical terminal can turn a small fault into a multi-day outage.

The evidence does not show which version is true. There is no public technician roster, service-level agreement, trouble-ticket data, spare-router inventory, optical-splicer inventory, vehicle list, after-hours escalation tree or average repair time. The field-repair score must therefore remain unverified. The site can claim service. The public record cannot yet grade repair capacity.

Installed addresses are not the same thing as usable capacity

The IPv4 block is the easiest part to count. A /23 contains 512 addresses. For a small retail access provider, that may be plenty of public numbering. It can support routers, customer public IP assignments, infrastructure, management hosts, business customers and future growth. It can also sit mostly unused if many customers are behind carrier-grade network address translation or if the block is reserved for planned expansion.

Address count is not bandwidth. A 100Mbps tariff does not imply that every customer has a dedicated 100Mbps path to the global internet at all times. Broadband networks work by statistical sharing: customers buy headline access rates, and the provider sizes aggregation and upstream capacity for expected busy-hour demand. Good engineering keeps congestion within acceptable limits. Weak engineering sells more peak demand than the feeder, switch or upstream circuit can carry.

The public sources do not disclose Ibroadband's upstream commit, oversubscription ratio, peak traffic, customer count, average utilisation, access technology, backhaul rate or congestion history. RIPEstat's routing-status result for AS138296 shows the origin network visible to all listed RIPE RIS peers, with 138 IPv4 prefixes and two IPv6 prefixes at the queried snapshot. That tells us Juweriyah is a live internet routing system. It does not tell us how much capacity is committed to Ibroadband customers, whether Ibroadband traffic is isolated, or whether the local access side can sustain every advertised plan.

TRAI's Quality of Service regulation is a useful way to think about the missing measurements. It focuses attention on delivered speed, latency, packet loss, jitter, service activation, fault repair and network performance between customer-serving nodes and the provider gateway or exchange link. Those are the numbers a customer actually feels. Ibroadband does not publish a public QoS report by those measures, and the national regulator's broad market publications do not supply an address-level view of this provider.

The package table does give an economics signal. A 5Mbps monthly plan at INR500 and a 100Mbps monthly plan at INR2,500 are not enterprise leased-line prices. They look like neighbourhood broadband rates aimed at households and small businesses. In that price band, repair labour, upstream transit, payment collection, customer-premises equipment and building access can matter as much as raw IP capacity. A provider can have a valid APNIC allocation and still lose money on a difficult building if repeated faults consume technician hours.

The payment portal's "thousands of clients" claim should be treated as a hypothesis. It may reflect real customer history, current accounts, associated network customers, a copied marketing phrase or a number that has changed. It is not accompanied by a date, audited subscriber table or regulator row. If thousands of active Mumbai users are indeed served under this brand, the network should have visible operational artefacts: current notices, service area detail, customer documentation, more explicit legal terms, active support pages, social updates, public outage information or stronger routing information.

Some of those may exist outside the public web; they are not visible in the available public sources.

The capacity conclusion is therefore modest. Ibroadband's public offer reaches 100Mbps, and its registered address space is enough for a small ISP. The usable capacity behind those facts is unknown. The route that is visible depends on AS138296. The access plant that customers touch is not publicly mapped. The bill can buy service; the evidence does not yet show the service's headroom.

Power and facilities are ordinary dependencies with outsized effect

Kurla West is not a remote greenfield market. It is a dense Mumbai neighbourhood with mixed residential, commercial and street-level activity. That density can help a small broadband provider because a short cable path may reach many accounts. It can hurt resilience because cable routes, building entrances, public power, roof access and street works are crowded.

The public record does not identify Ibroadband's network room. The shop address on the website is shop no. 7 on A.H. Wadia Marg; APNIC records use shop no. 8 near Habib Hospital; the route-origin ASN's APNIC record points to shop no. 3 at Ibrahim Chunawala Plot near the bus depot. Those addresses are close in the same Kurla West operating area, but a contact address is not necessarily a point of presence. It can be a billing office, a customer counter, a registered contact point, a router location or only an administrative surface.

Without a site photo, facility lease, rack note or maintenance notice, the equipment location remains unknown.

That uncertainty changes the power analysis. If routers, optical terminals and aggregation switches sit in a small shop, the provider needs stable mains power, surge protection, battery backup and perhaps generator access. If the key electronics sit in a partner facility, the provider's own shop power may not decide network uptime. If customer buildings hold distribution switches, then each building's power and landlord access become part of the service chain. The public evidence does not disclose which design is in use.

Power is often the hidden broadband dependency because the physical fibre can be intact while active equipment is off. A passive optical splitter does not need power in the field, but optical-line terminals, aggregation switches, routers, wireless radios, payment servers, customer Wi-Fi routers and monitoring systems do. Small providers may rely on modest UPS units rather than long-runtime backup systems. If a failure lasts beyond battery life, a network that looked redundant in routing can still go dark at the access layer.

The website gives no backup-power promise. It does not specify UPS duration, generator availability, battery replacement, climate control, remote monitoring or emergency fuel. That is not unusual for a small retail site. It is still material. A customer deciding whether a line can support business-critical work should know whether the provider can keep equipment alive through local interruptions and whether the customer's own premises also have power protection.

The facility question is also tied to repair. If the key cabinet or router is in a shop controlled by the operator, a technician can reach it quickly. If equipment sits behind a landlord gate, on a roof, in a locked telecom room or in another operator's facility, after-hours access can become the bottleneck. Public sources do not reveal those access rights. The public record cannot therefore endorse a recovery time. It can only identify the recovery chain that should be verified.

Upstream loss is the cleanest failure path

The cleanest failure path is upstream loss, because it is visible in public routing. Ibroadband's own AS141245 has no observed neighbours. Its registered /23 is announced by Juweriyah's AS138296. If that AS138296-originated route disappears and no AS141245-originated route replaces it, the public internet loses reachability to the Ibroadband-numbered addresses. If AS138296 has congestion or filtering that affects the relevant route, Ibroadband customers using those addresses may feel it even if the local drop is intact.

The exact customer impact depends on how addresses are allocated. If customers use public IPs from 103.157.178.0/23, a withdrawal of those routes can disrupt inbound and outbound reachability. If customers are behind private addresses and translated through another pool, the effect may differ. If the block is used only for infrastructure, the customer impact may be indirect. Public sources do not map address utilisation, so the conclusion should not say every customer sits on the /23.

What can be said is that the visible redundancy test fails for Ibroadband's own autonomous system. There is no public second upstream for AS141245, no visible BGP session, no PeeringDB network record and no currently announced Ibroadband-originated prefix. Juweriyah's AS138296 has observed neighbours and exchange presence, but those are not automatically Ibroadband's redundancy. A managed upstream can have robust external connectivity while the customer handoff into that upstream remains a single port, single cross-connect, single cable, single switch or single commercial relationship.

This is a common small-ISP problem. Buying service from a larger local operator can improve reach and lower capital costs, but it shifts part of the resilience question outside the retail brand. The customer may call Ibroadband; Ibroadband may need Juweriyah or another operator to restore the upstream route. If the arrangement is formal, monitored and backed by support commitments, this can work well. If it is informal or dependent on one shared device, failures can be slow to isolate.

The public record also leaves IPv6 uncertain. AS141245 has no visible IPv6 route. Juweriyah's AS138296 does announce some IPv6 space according to RIPEstat, but there is no public evidence that Ibroadband customers receive IPv6, that 103.157.178.0/23 has a parallel IPv6 customer deployment, or that customer equipment is dual-stack. For modern applications, lack of IPv6 is not always fatal, but it can affect performance, future-proofing and address-management economics.

The practical verification task is simple: ask for a current traceroute from an Ibroadband customer, the customer public IP range, the BGP origin expected for that range, the upstream provider name, the failover provider if any, and the restoration process if AS138296 withdraws the route. Without those answers, the safest public statement is dependence, not diversity.

Who is affected if the service fails

The first affected users are the paying customers on the Ibroadband brand: households, small businesses and any corporate users the site describes. The package table suggests residential and small-office broadband. The payment portal suggests ongoing account relationships. The website's city-only language suggests a Mumbai service area, not a national base. The conclusion should therefore avoid language that implies a state-wide or all-India customer impact.

The second affected group is local businesses that treat a small broadband line as primary connectivity. In dense urban neighbourhoods, a shop, clinic, travel office, tuition centre, warehouse desk or professional service can run payments, messaging, inventory and video calls over one affordable line. The plan table's pricing makes that plausible. The evidence does not identify named customers, so none should be named. But the service category itself makes the dependency reasonable.

The third affected group is the operator chain behind the route. If Ibroadband has customers using its APNIC space through AS138296, then Juweriyah's routing, monitoring and support practices affect those customers. If there is a shared ownership, partnership or wholesale arrangement, the operational impact may be coordinated. If not, escalation can take longer. The public sources show technical adjacency and overlapping local contact signals; they do not disclose commercial terms.

There are also indirect effects. A local network that sells through selected entrepreneurs depends on those entrepreneurs for installs, collections, first-line support and local trust. If an entrepreneur leaves, loses access to a building, or cannot get spares, customers may not care which ASN is visible. They care whether the person who knows their cable path can repair it. A provider with a small service area can benefit from local knowledge, but it can also be exposed to local labour bottlenecks.

The failure should not be dramatised beyond the evidence. There is no public outage record here, no complaint dataset, no regulator penalty and no published customer count. The risk is structural, not a documented incident. The structure is enough for an evidence-grade downgrade because the public proof needed to evaluate resilience is missing at every layer: serviceable footprint, route diversity, field repair, backup power and legal operating boundary.

What would upgrade the evidence

Ibroadband could move from Weak to Medium evidence without publishing every commercial secret. A current licence or authorisation statement tied to the retail name would settle the legal boundary. A support or terms page naming the licensed operator behind the brand would be nearly as useful. A simple service-area page listing neighbourhoods, not individual customers, would improve the access footprint. A maintenance page or status channel would show an operating rhythm.

The routing upgrade is equally clear. If AS141245 originates 103.157.178.0/23 or its /24 components again, public route collectors would show it. If AS141245 becomes multi-homed, RIPEstat would show neighbours. If the design intentionally keeps AS138296 as the origin, a public note could explain that Juweriyah provides upstream routing for Ibroadband-numbered space. That would not prove physical diversity, but it would turn an unexplained dependency into an understood operator boundary.

The field-repair upgrade needs less public routing and more physical evidence. A service-level promise, technician coverage hours, customer equipment replacement policy, building-access process, spare-stock practice, and escalation path for upstream or power failures would tell customers what happens after the phone call. A provider can be small and still reliable if it knows its routes and owns its repair process.

The commercial upgrade would be just as important. A small provider can be technically sound and still fragile if collections, renewals and customer records sit in a brittle local payment process. The payment portal shows that Ibroadband has an account-facing path, but it does not show how disputes, duplicate transactions, failed payments, disconnections or plan changes are reconciled with the field team. In a very local broadband design, billing and repair can become the same operational problem: the customer who cannot pay online may also be the customer whose account status prevents a technician from accepting a fault report.

A current support policy would reduce that uncertainty.

The customer-premises boundary also deserves evidence. Broadband failures are often blamed on the provider when the fault is a loose indoor cable, ageing Wi-Fi router, power adapter, damaged optical network terminal or building switch. A resilient small ISP needs a clear demarcation point: what belongs to the customer, what belongs to the building, what belongs to the local operator, and what belongs to the upstream network. Ibroadband's public pages do not define that handoff. A simple installation guide, equipment responsibility note or replacement policy would make the service more legible without exposing sensitive network design.

The strongest upgrade would be a short current operating disclosure tying all these layers together: legal provider, brand, service area, support hours, upstream origin, expected customer IP ranges, repair process and power assumptions. That would not require publishing a private route map. It would simply let a customer or landlord understand whether the line is a standalone Ibroadband service, a Juweriyah-backed service under an Ibroadband brand, or another local arrangement. At present, the public evidence supports service, but not enough accountability mapping.

Capacity evidence would come from measurements rather than slogans. TRAI-style speed, latency, packet-loss and restoration metrics by plan or area would matter more than another headline speed. Even a limited public explanation of busy-hour management and fair-use policy would help. The current package table gives price and speed; it does not show delivered service quality.

Power evidence would come from backup-runtime statements for any central equipment, not from generic reliability language. If a local aggregation switch has two hours of UPS and a generator option, that is useful. If building switches rely on customer or landlord power, customers should know. If the upstream handoff is in a facility with stronger backup, that helps, but only if the path from customer to facility is also protected.

Until those facts appear, the operating thesis must stay downgraded. Ibroadband Internet Service is visible enough to be treated as a Mumbai broadband provider, but not visible enough to be treated as an independently routed regional ISP. The local bill depends on a chain: the customer's drop, the building or street access path, the field technician, the power environment, the upstream route through AS138296, and the unresolved legal/operator boundary behind the brand.

Evidence-bound downgrade

The regional-ISP thesis is partially supported and partially unsupported. It is supported by Ibroadband's live website, online payment portal, Mumbai-only service language, public package table, APNIC ASN, APNIC IPv4 allocation and the active visibility of that allocation through a nearby ISP ASN. It is unsupported if "regional ISP" means an independently routed operator with public proof of its own BGP edge, clear licence identity, audited subscriber base, mapped access plant, route diversity and documented field recovery.

The strongest public facts are operational but not complete. The domain is registered through 2028. The package page offers affordable plans. The payment portal is built for existing account lookup. APNIC continues to carry Ibroadband contacts and active number resources. RIPEstat sees the address space in global routing. These are positive signs.

The strongest negative facts are also operational. AS141245 is not visible. The prefix is originated by AS138296. PeeringDB has a network entry for AS138296, not for AS141245. DoT authorisation evidence under the Ibroadband trading name is not public in the files reviewed here. No public data verifies current customer count, repair staff, route diversity, backup power, physical handoff location or service quality.

That combination lands at Weak, not Negative. Negative would imply the public record contradicts the existence of service. It does not. The public record instead shows a service brand with real contact, billing and number-resource surfaces, while leaving the engineering and legal responsibility chain under-specified. The public profile should not remove the company from a regional-ISP category, but it should mark the category as a low-confidence operating lens rather than a settled infrastructure claim.

For a customer, the question is practical: who repairs the line, who controls the route, and what happens when the upstream path or local power fails? The public record answers only part of that. It says where the brand is, what it sells, what number resources are allocated and which ASN currently originates the address block. It does not yet say enough about the people, spares, contracts and physical paths that decide whether the next outage is measured in minutes, hours or days.