bgpreport

Network · data from 2026-11-12

AS56264 Tomato Web Limited

Registry name: TOMATOWEB-BD - Tomato Web (Pvt) Limited, BD · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS56264, 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.

81.168.71.0/24 Invalid: origin Other origin only 2 0%low visibility 2
81.168.77.0/24 Invalid: origin Other origin only 2 0%low visibility 2
82.152.252.0/24 Invalid: origin Other origin only 2 0%low visibility 2
81.168.42.0/24 Valid Other IRR onlyRADB 673 100% 68
81.168.43.0/24 Valid Other IRR onlyRADB 673 100% 68
81.168.78.0/24 Valid Other IRR onlyRADB 673 100% 68
82.152.28.0/24 Valid Other IRR onlyRADB 673 100% 66
82.152.83.0/24 Valid Other IRR onlyRADB 673 100% 66
82.152.115.0/24 Valid Other IRR onlyRADB 673 100% 66
82.152.120.0/24 Valid Other IRR onlyRADB 673 100% 66
82.152.130.0/24 Valid Other IRR onlyRADB 673 100% 66
82.152.196.0/24 Valid Other IRR onlyRADB 673 100% 68
82.152.201.0/24 Valid Other IRR onlyRADB 673 100% 68
82.152.202.0/24 Valid Other IRR onlyRADB 673 100% 68
82.152.203.0/24 Valid Other IRR onlyRADB 673 100% 68
82.152.204.0/24 Valid Other IRR onlyRADB 673 100% 68
82.152.205.0/24 Valid Other IRR onlyRADB 673 100% 68
82.152.206.0/24 Valid Other IRR onlyRADB 673 100% 68
82.152.207.0/24 Valid Other IRR onlyRADB 673 100% 68
82.152.249.0/24 Valid Other IRR onlyRADB 673 100% 66
82.152.250.0/24 Valid Other IRR onlyRADB 673 100% 66
82.152.251.0/24 Valid Other IRR onlyRADB 673 100% 66
82.152.253.0/24 Valid Other IRR onlyRADB 673 100% 66
82.152.254.0/24 Valid Other IRR onlyRADB 673 100% 66
82.152.255.0/24 Valid Other IRR onlyRADB 673 100% 66
82.153.51.0/24 Valid Other IRR onlyRADB 673 100% 66
82.153.154.0/24 Valid Other IRR onlyRADB 673 100% 66
89.213.52.0/24 Valid Other IRR onlyRADB 673 100% 68
89.213.53.0/24 Valid Other IRR onlyRADB 673 100% 68
89.213.54.0/24 Valid Other IRR onlyRADB 673 100% 68
89.213.55.0/24 Valid Other IRR onlyRADB 673 100% 68
89.213.56.0/24 Valid Other IRR onlyRADB 673 100% 68
89.213.57.0/24 Valid Other IRR onlyRADB 673 100% 68
89.213.59.0/24 Valid Other IRR onlyRADB 673 100% 68
89.213.60.0/24 Valid Other IRR onlyRADB 673 100% 68
89.213.61.0/24 Valid Other IRR onlyRADB 673 100% 68
89.213.97.0/24 Valid Other IRR onlyRADB 673 100% 68
89.213.99.0/24 Valid Other IRR onlyRADB 673 100% 68
89.213.104.0/24 Valid Other IRR onlyRADB 673 100% 68
89.213.105.0/24 Valid Other IRR onlyRADB 673 100% 68
89.213.107.0/24 Valid Other IRR onlyRADB 673 100% 68
81.168.60.0/24 Valid Other IRR onlyRADB 671 100% 68
36.50.102.0/24 Valid RIR databaseAPNIC 673 100% 69
36.50.103.0/24 Valid RIR databaseAPNIC 673 100% 69
103.163.31.0/24 Valid RIR databaseAPNIC 673 100% 69
103.189.6.0/24 Valid RIR databaseAPNIC 673 100% 66
103.189.7.0/24 Valid RIR databaseAPNIC 673 100% 66
103.190.74.0/24 Valid RIR databaseAPNIC 673 100% 69
103.190.75.0/24 Valid RIR databaseAPNIC 673 100% 67
210.79.181.0/24 Valid RIR databaseAPNIC 673 100% 69
103.6.160.0/24 Valid RIR databaseAPNIC 672 100% 67
103.37.184.0/24 Valid RIR databaseAPNIC 672 100% 67
103.163.30.0/24 Valid RIR databaseAPNIC 672 100% 67
103.173.100.0/24 Valid RIR databaseAPNIC 672 100% 67
103.173.101.0/24 Valid RIR databaseAPNIC 672 100% 67
106.0.60.0/24 Valid RIR databaseAPNIC, RADB 672 100% 67
106.0.61.0/24 Valid RIR databaseAPNIC 672 100% 67
165.99.196.0/24 Valid RIR databaseAPNIC 672 100% 67
165.99.197.0/24 Valid RIR databaseAPNIC 672 100% 66
103.40.53.0/24 Valid RIR databaseAPNIC 667 99% 69
2406:9b00::/48 Valid RIR databaseAPNIC 636 100% 70
2401:9440::/33 Valid RIR databaseAPNIC 635 100% 69
2401:9440:8000::/33 Valid RIR databaseAPNIC 635 100% 69
2406:9b00:1000::/36 Valid RIR databaseAPNIC 635 100% 69
2406:9b00:2000::/36 Valid RIR databaseAPNIC 635 100% 69
2406:9b00:3000::/36 Valid RIR databaseAPNIC 635 100% 69
2406:9b00:4000::/36 Valid RIR databaseAPNIC 635 100% 69
2406:9b00:5000::/36 Valid RIR databaseAPNIC 635 100% 69
2406:9b00:6000::/36 Valid RIR databaseAPNIC 635 100% 69
2406:9b00:7000::/36 Valid RIR databaseAPNIC 635 100% 69
2406:9b00:8000::/33 Valid RIR databaseAPNIC 3 0%low visibility 4

AS-SET

PeeringDB's irr_as_set for AS56264: AS56264. 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 (AS56264 isn't in the set, or no route object for AS56264 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 objectsAS56264 in itNot covered
AS56264 A single AS number, not a set: AS56264 (this network), 83 route objects.

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 60 are in fix.csv.

  • ROA: origin3
  • Route object: none3
  • Route object: RIR39
  • Route object: not announced15
ChangePrefix or setDetailFull-table peers
ROA: origin81.168.71.0/24ROAs covering it name AS834, AS8851, AS19905, AS206509, not AS56264. If AS56264 should announce it, add a ROA for AS56264.2 of 673
Route object: none81.168.71.0/24Route objects for it name AS834. Add a route object with origin AS56264 in the RIR database for the space.2 of 673
ROA: origin81.168.77.0/24ROAs covering it name AS834, AS8851, AS19905, AS206509, not AS56264. If AS56264 should announce it, add a ROA for AS56264.2 of 673
Route object: none81.168.77.0/24Route objects for it name AS834. Add a route object with origin AS56264 in the RIR database for the space.2 of 673
ROA: origin82.152.252.0/24ROAs covering it name AS8851, AS19905, AS20473, AS206509, not AS56264. If AS56264 should announce it, add a ROA for AS56264.2 of 673
Route object: none82.152.252.0/24Route objects for it name AS20473. Add a route object with origin AS56264 in the RIR database for the space.2 of 673
Route object: RIR81.168.42.0/24Route object only in RADB. Add it in the RIR database for the space.673 of 673
Route object: RIR81.168.43.0/24Route object only in RADB. Add it in the RIR database for the space.673 of 673
Route object: RIR81.168.78.0/24Route object only in RADB. Add it in the RIR database for the space.673 of 673
Route object: RIR82.152.28.0/24Route object only in RADB. Add it in the RIR database for the space.673 of 673
Route object: RIR82.152.83.0/24Route object only in RADB. Add it in the RIR database for the space.673 of 673
Route object: RIR82.152.115.0/24Route object only in RADB. Add it in the RIR database for the space.673 of 673
Route object: RIR82.152.120.0/24Route object only in RADB. Add it in the RIR database for the space.673 of 673
Route object: RIR82.152.130.0/24Route object only in RADB. Add it in the RIR database for the space.673 of 673
Route object: RIR82.152.196.0/24Route object only in RADB. Add it in the RIR database for the space.673 of 673
Route object: RIR82.152.201.0/24Route object only in RADB. Add it in the RIR database for the space.673 of 673
Route object: RIR82.152.202.0/24Route object only in RADB. Add it in the RIR database for the space.673 of 673
Route object: RIR82.152.203.0/24Route object only in RADB. Add it in the RIR database for the space.673 of 673
Route object: RIR82.152.204.0/24Route object only in RADB. Add it in the RIR database for the space.673 of 673
Route object: RIR82.152.205.0/24Route object only in RADB. Add it in the RIR database for the space.673 of 673
Route object: RIR82.152.206.0/24Route object only in RADB. Add it in the RIR database for the space.673 of 673
Route object: RIR82.152.207.0/24Route object only in RADB. Add it in the RIR database for the space.673 of 673
Route object: RIR82.152.249.0/24Route object only in RADB. Add it in the RIR database for the space.673 of 673
Route object: RIR82.152.250.0/24Route object only in RADB. Add it in the RIR database for the space.673 of 673
Route object: RIR82.152.251.0/24Route object only in RADB. Add it in the RIR database for the space.673 of 673
Route object: RIR82.152.253.0/24Route object only in RADB. Add it in the RIR database for the space.673 of 673
Route object: RIR82.152.254.0/24Route object only in RADB. Add it in the RIR database for the space.673 of 673
Route object: RIR82.152.255.0/24Route object only in RADB. Add it in the RIR database for the space.673 of 673
Route object: RIR82.153.51.0/24Route object only in RADB. Add it in the RIR database for the space.673 of 673
Route object: RIR82.153.154.0/24Route object only in RADB. Add it in the RIR database for the space.673 of 673
Route object: RIR89.213.52.0/24Route object only in RADB. Add it in the RIR database for the space.673 of 673
Route object: RIR89.213.53.0/24Route object only in RADB. Add it in the RIR database for the space.673 of 673
Route object: RIR89.213.54.0/24Route object only in RADB. Add it in the RIR database for the space.673 of 673
Route object: RIR89.213.55.0/24Route object only in RADB. Add it in the RIR database for the space.673 of 673
Route object: RIR89.213.56.0/24Route object only in RADB. Add it in the RIR database for the space.673 of 673
Route object: RIR89.213.57.0/24Route object only in RADB. Add it in the RIR database for the space.673 of 673
Route object: RIR89.213.59.0/24Route object only in RADB. Add it in the RIR database for the space.673 of 673
Route object: RIR89.213.60.0/24Route object only in RADB. Add it in the RIR database for the space.673 of 673
Route object: RIR89.213.61.0/24Route object only in RADB. Add it in the RIR database for the space.673 of 673
Route object: RIR89.213.97.0/24Route object only in RADB. Add it in the RIR database for the space.673 of 673
Route object: RIR89.213.99.0/24Route object only in RADB. Add it in the RIR database for the space.673 of 673
Route object: RIR89.213.104.0/24Route object only in RADB. Add it in the RIR database for the space.673 of 673
Route object: RIR89.213.105.0/24Route object only in RADB. Add it in the RIR database for the space.673 of 673
Route object: RIR89.213.107.0/24Route object only in RADB. Add it in the RIR database for the space.673 of 673
Route object: RIR81.168.60.0/24Route object only in RADB. Add it in the RIR database for the space.671 of 673

Route objects not announced

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

36.50.102.0/23APNICValid
72.244.32.0/22ARIN, RADBValid
103.40.52.0/23APNICValid
103.40.52.0/24APNICValid
202.50.155.0/24APNICValid
2406:9b00::/33APNICValid
2406:9b00::/34APNICValid
2406:9b00::/35APNICValid
2406:9b00::/36APNICValid
2406:9b00:1::/48APNICValid
2406:9b00:2::/48APNICValid
2406:9b00:2000::/35APNICValid
2406:9b00:4000::/34APNICValid
2406:9b00:4000::/35APNICValid
2406:9b00:6000::/35APNICValid

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.