bgpreport

Network · data from 2026-11-12

AS45356 Mobitel Sri Lanka

Registry name: MOBITEL-LK - Mobitel Pvt Ltd, LK · PeeringDB

60IPv4 routes 100.0% RPKI valid · 100.0% with a route object
5IPv6 routes 100.0% RPKI valid · 100.0% with a route object
0RPKI invalid 0 origin · 0 maxLength
0No ROA 0 with no route object for this origin
52Low visibility seen by under 10% of full-table peers
71Route objects not announced registered with origin AS45356, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS45356, things to look at first. Visibility = full-table peers that see it, of 673 (IPv4) and 636 (IPv6) on 75 collectors. Also as routes.csv.

43.250.240.0/22 Valid RIR databaseAPNIC 673 100% 66
61.245.160.0/20 Valid RIR databaseAPNIC 673 100% 66
103.2.152.0/22 Valid RIR databaseAPNIC 673 100% 66
124.6.240.0/20 Valid RIR databaseAPNIC 673 100% 66
194.140.200.0/21 Valid RIR databaseAPNIC 673 100% 66
194.140.200.0/24 Valid RIR databaseAPNIC 673 100% 66
194.140.201.0/24 Valid RIR databaseAPNIC 673 100% 66
194.140.207.0/24 Valid RIR databaseAPNIC 673 100% 66
202.129.232.0/22 Valid RIR databaseAPNIC, RADB 673 100% 66
202.129.232.0/23 Valid RIR databaseAPNIC 673 100% 66
202.129.234.0/23 Valid RIR databaseAPNIC 673 100% 66
212.104.224.0/20 Valid RIR databaseAPNIC 673 100% 66
2407:c00::/32 Valid RIR databaseAPNIC 635 100% 69
43.250.240.0/24 Valid RIR databaseAPNIC 41 6%low visibility 29
61.245.160.0/24 Valid RIR databaseAPNIC 41 6%low visibility 29
61.245.161.0/24 Valid RIR databaseAPNIC 41 6%low visibility 29
61.245.162.0/24 Valid RIR databaseAPNIC 41 6%low visibility 29
61.245.163.0/24 Valid RIR databaseAPNIC 41 6%low visibility 29
61.245.165.0/24 Valid RIR databaseAPNIC 41 6%low visibility 29
61.245.166.0/24 Valid RIR databaseAPNIC 41 6%low visibility 29
61.245.167.0/24 Valid RIR databaseAPNIC 41 6%low visibility 29
61.245.168.0/24 Valid RIR databaseAPNIC 41 6%low visibility 29
61.245.169.0/24 Valid RIR databaseAPNIC 41 6%low visibility 29
61.245.170.0/24 Valid RIR databaseAPNIC 41 6%low visibility 29
61.245.172.0/24 Valid RIR databaseAPNIC 41 6%low visibility 29
61.245.173.0/24 Valid RIR databaseAPNIC 41 6%low visibility 29
61.245.174.0/24 Valid RIR databaseAPNIC 41 6%low visibility 29
61.245.175.0/24 Valid RIR databaseAPNIC 41 6%low visibility 29
103.2.152.0/24 Valid RIR databaseAPNIC 41 6%low visibility 29
103.2.155.0/24 Valid RIR databaseAPNIC 41 6%low visibility 29
202.129.232.0/24 Valid RIR databaseAPNIC 41 6%low visibility 29
202.129.233.0/24 Valid RIR databaseAPNIC 41 6%low visibility 29
202.129.234.0/24 Valid RIR databaseAPNIC 41 6%low visibility 29
202.129.235.0/24 Valid RIR databaseAPNIC 41 6%low visibility 29
212.104.228.0/24 Valid RIR databaseAPNIC 41 6%low visibility 29
212.104.229.0/24 Valid RIR databaseAPNIC 41 6%low visibility 29
212.104.231.0/24 Valid RIR databaseAPNIC 41 6%low visibility 29
2407:c00::/34 Valid RIR databaseAPNIC 38 6%low visibility 27
2407:c00:4000::/34 Valid RIR databaseAPNIC 38 6%low visibility 27
2407:c00:8000::/34 Valid RIR databaseAPNIC 38 6%low visibility 27
2407:c00:c000::/34 Valid RIR databaseAPNIC 38 6%low visibility 27
194.140.202.0/24 Valid RIR databaseAPNIC 2 0%low visibility 2
194.140.203.0/24 Valid RIR databaseAPNIC 2 0%low visibility 2
194.140.204.0/24 Valid RIR databaseAPNIC 2 0%low visibility 2
43.250.241.0/24 Valid RIR databaseAPNIC 0 0%low visibility 1
43.250.242.0/24 Valid RIR databaseAPNIC 0 0%low visibility 1
43.250.243.0/24 Valid RIR databaseAPNIC 0 0%low visibility 1
61.245.160.0/22 Valid RIR databaseAPNIC 0 0%low visibility 1
61.245.164.0/22 Valid RIR databaseAPNIC 0 0%low visibility 1
61.245.168.0/22 Valid RIR databaseAPNIC 0 0%low visibility 1
61.245.171.0/24 Valid RIR databaseAPNIC 0 0%low visibility 1
61.245.172.0/22 Valid RIR databaseAPNIC 0 0%low visibility 1
212.104.224.0/24 Valid RIR databaseAPNIC 0 0%low visibility 1
212.104.225.0/24 Valid RIR databaseAPNIC 0 0%low visibility 1
212.104.226.0/24 Valid RIR databaseAPNIC 0 0%low visibility 1
212.104.227.0/24 Valid RIR databaseAPNIC 0 0%low visibility 1
212.104.230.0/24 Valid RIR databaseAPNIC 0 0%low visibility 1
212.104.232.0/24 Valid RIR databaseAPNIC 0 0%low visibility 1
212.104.233.0/24 Valid RIR databaseAPNIC 0 0%low visibility 1
212.104.234.0/24 Valid RIR databaseAPNIC 0 0%low visibility 1
212.104.235.0/24 Valid RIR databaseAPNIC 0 0%low visibility 1
212.104.236.0/24 Valid RIR databaseAPNIC 0 0%low visibility 1
212.104.237.0/24 Valid RIR databaseAPNIC 0 0%low visibility 1
212.104.238.0/24 Valid RIR databaseAPNIC 0 0%low visibility 1
212.104.239.0/24 Valid RIR databaseAPNIC 0 0%low visibility 1

AS-SET

PeeringDB's irr_as_set for AS45356: AS45356:AS-13335. Expanded from the day's IRR dumps the way bgpq4 does against whois.radb.net: a name with a database is read from that database only, one without from the first database in RADB's order. "Not covered" = this network's own routes that a filter built from the set would leave out (AS45356 isn't in the set, or no route object for AS45356 covers the route; more-specifics of a route object are accepted down to /24 and /48, as with bgpq4 -A -R 24 / -R 48). Customers' routes aren't counted: the collectors show each route's origin, not which network it came through.

NameDatabaseASNsSets Route objectsAS45356 in itNot covered
AS45356:AS-13335 APNIC 313,253 Yes 0

Fix list

The changes that would bring RPKI, the IRR and what's announced into line. Some are deliberate (a route object kept for a backup route, say); the network decides. All 71 are in fix.csv.

  • Route object: not announced71

Route objects not announced

Route objects with origin AS45356 whose prefix no peer sees AS45356 announce. Many are kept on purpose (backup routes, space announced only in some places).

43.250.240.0/23APNICValid
43.250.242.0/23APNICValid
61.245.160.0/21APNICValid
61.245.160.0/23APNICValid
61.245.162.0/23APNICValid
61.245.164.0/23APNICValid
61.245.164.0/24APNICValid
61.245.166.0/23APNICValid
61.245.168.0/21APNICValid
61.245.168.0/23APNICValid
61.245.170.0/23APNICValid
61.245.172.0/23APNICValid
61.245.174.0/23APNICValid
103.2.152.0/23APNICValid
103.2.153.0/24APNICValid
103.2.154.0/23APNICValid
103.2.154.0/24APNICValid
124.6.240.0/21APNICValid
124.6.240.0/22APNICValid
124.6.240.0/23APNICValid
124.6.240.0/24APNICValid
124.6.241.0/24APNICValid
124.6.242.0/23APNICValid
124.6.242.0/24APNICValid
124.6.243.0/24APNICValid
124.6.244.0/22APNICValid
124.6.244.0/23APNICValid
124.6.244.0/24APNICValid
124.6.245.0/24APNICValid
124.6.246.0/23APNICValid
124.6.246.0/24APNICValid
124.6.247.0/24APNICValid
124.6.248.0/21APNICValid
124.6.248.0/22APNICValid
124.6.248.0/23APNICValid
124.6.248.0/24APNICValid
124.6.249.0/24APNICValid
124.6.250.0/23APNICValid
124.6.250.0/24APNICValid
124.6.251.0/24APNICValid
124.6.252.0/22APNICValid
124.6.252.0/23APNICValid
124.6.252.0/24APNICValid
124.6.253.0/24APNICValid
124.6.254.0/23APNICValid
124.6.254.0/24APNICValid
124.6.255.0/24APNICValid
194.140.200.0/22APNICValid
194.140.200.0/23APNICValid
194.140.202.0/23APNICValid
194.140.204.0/22APNICValid
194.140.204.0/23APNICValid
194.140.205.0/24APNICValid
194.140.206.0/23APNICValid
194.140.206.0/24APNICValid
212.104.224.0/21APNICValid
212.104.224.0/22APNICValid
212.104.224.0/23APNICValid
212.104.226.0/23APNICValid
212.104.228.0/22APNICValid
212.104.228.0/23APNICValid
212.104.230.0/23APNICValid
212.104.232.0/21APNICValid
212.104.232.0/22APNICValid
212.104.232.0/23APNICValid
212.104.234.0/23APNICValid
212.104.236.0/22APNICValid
212.104.236.0/23APNICValid
212.104.238.0/23APNICValid
2407:c00::/33APNICValid
2407:c00:8000::/33APNICValid

Routes: the 08:00 UTC snapshots of 2026-11-12 from 75 RIPE RIS and RouteViews collectors. RPKI: our rpki-client run before the snapshot. IRR: the day's dumps of the five RIR databases and RADB's mirrors. The LEVEL3 and IDNIC databases publish no dump and aren't read, so route objects only there count as none.