AS17806Mango Teleservices
As of 10th November 2026, AS17806 (Mango Teleservices), a transit carrier registered in Bangladesh with APNIC, originates 87 IPv4 prefixes covering 54.8k addresses and 13 IPv6 prefixes. By IPv4 address space that makes it the 4,324th-largest of the 80,723 networks we see originating IPv4, and the 9th-largest of 1,567 in Bangladesh. It is seen behind 21 upstream networks, most often AS9583 (Sify Limited) and AS132602 (Bangladesh Submarine Cable Company…), and in front of 22 downstream networks. Every one of its announcements has a valid RPKI ROA, and none are RPKI-invalid. 97% of its routes reach at least 90% of full-feed peers.
At a glance
IPv4 prefixes
IPv6 prefixes
IPv4 addresses
IPv6 /64s
Upstream graph
The networks AS17806 is seen behind, one and two hops out, drawn from real AS paths.
Networks observed one and two hops upstream of AS17806 in real AS paths. A thicker line means more vantage points saw that adjacency, so weight tracks how well attested it is — not how much traffic it carries. Adjacency is an observation; whether it is a transit purchase or a settlement-free peering is an inference, and is labelled as one wherever we show it.
Neighbouring networks
105
adjacent networks
- Upstreams
- 2120%
- Peers
- 6259%
- Downstreams
- 2221%
Networks carrying this one's traffic toward the rest of the internet.
| Network | Country | Relationship | Paths | Vantage pts |
|---|---|---|---|---|
| AS9583Sify Limited | Peer | 8,541 | 139 | |
| AS132602Bangladesh Submarine Cable Company Limited (BSCCL) | Peer | 5,923 | 138 | |
| AS6939Hurricane Electric LLC | Peer | 1,606 | 114 | |
| AS3223Voxility LLP | Peer | 195 | 76 | |
| AS174Cogent Communications, LLC | Peer | 193 | 48 | |
| AS132337Axclusive | Adjacent | 142 | 2 | |
| AS17660DrukNet ISP | Adjacent | 42 | 2 | |
| AS58778Mango Teleservices Limited for ITC | Peer | 26 | 26 | |
| AS7713PT Telkom Indonesia Tbk | Adjacent | 8 | 2 | |
| AS14537Continent 8 LLC | Peer | 8 | 2 |
Prefixes
All 100The largest blocks AS17806 originates, widest first.
| Prefix | Addresses | Visibility |
|---|---|---|
| 114.130.0.0/17 | 32.8k | 13/76 |
| 114.130.0.0/24 | 256 | 76/76 |
| 114.130.1.0/24 | 256 | 76/76 |
| 114.130.2.0/24 | 256 | 76/76 |
| 114.130.3.0/24 | 256 | 76/76 |
| 114.130.6.0/24 | 256 | 76/76 |
| 114.130.7.0/24 | 256 | 76/76 |
| 114.130.8.0/24 | 256 | 76/76 |
| 114.130.9.0/24 | 256 | 76/76 |
| 114.130.10.0/24 | 256 | 76/76 |
Routing health
How AS17806's own announcements validate against RPKI and how far they propagate. The same measures for the whole routing table are on the routing table in numbers.
RPKI origin validation
- Valid100.0%100
- Invalid0.0%0
- No ROA0.0%0
Propagation
- Globally propagated90% of full-feed peers or more97.0%97
- Partially propagated40% to 90%1.0%1
- Seen by few peersUnder 40%2.0%2
Prefix sizes
IPv4 — 87 prefixes
IPv6 — 13 prefixes
- /324.3B × /647.7%1
- /36268M × /647.7%1
- /4865.5k × /6484.6%11
Recent changes
Announcements that started or stopped since 11th Oct 2026.
No announcement by AS17806 started or stopped in this period.
Routing data derived from RouteViews MRT archives, BGPKIT relationship inference and public registry data.