bgpreport

Network · data from 2026-11-12

AS136948 Today Vision

Registry name: TodayVision-BD - Today Vision, BD · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS136948, 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.
2401:b640:6::/48 Valid Nonecovered by 2401:b640::/32 635 100% 69
2401:b640:17::/48 Valid Nonecovered by 2401:b640::/32 635 100% 69
2401:b640:5::/48 Valid Nonecovered by 2401:b640::/32 1 0%low visibility 1
103.99.249.0/24 Valid RIR databaseAPNIC 673 100% 69
103.99.250.0/24 Valid RIR databaseAPNIC 673 100% 69
103.99.251.0/24 Valid RIR databaseAPNIC 673 100% 69
103.99.248.0/24 Valid RIR databaseAPNIC 672 100% 69
2401:b640::/48 Valid RIR databaseAPNIC 636 100% 70
2401:b640:1::/48 Valid RIR databaseAPNIC 636 100% 69
2401:b640:2::/48 Valid RIR databaseAPNIC 636 100% 69
2401:b640:3::/48 Valid RIR databaseAPNIC 636 100% 69
2401:b640::/32 Valid RIR databaseAPNIC 0 0%low visibility 1

AS-SET

PeeringDB's irr_as_set for AS136948: AS136948:AS-AP. 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 (AS136948 isn't in the set, or no route object for AS136948 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 objectsAS136948 in itNot covered
AS136948:AS-AP In no IRR database read today.

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

  • Route object: none3
  • AS-SET: not found1
  • Route object: not announced3
ChangePrefix or setDetailFull-table peers
Route object: none2401:b640:6::/48No route object for it. A route object for 2401:b640::/32 with origin AS136948 covers it (filters allowing more-specifics accept it). Add a route object with origin AS136948 in the RIR database for the space.635 of 636
Route object: none2401:b640:17::/48No route object for it. A route object for 2401:b640::/32 with origin AS136948 covers it (filters allowing more-specifics accept it). Add a route object with origin AS136948 in the RIR database for the space.635 of 636
Route object: none2401:b640:5::/48No route object for it. A route object for 2401:b640::/32 with origin AS136948 covers it (filters allowing more-specifics accept it). Add a route object with origin AS136948 in the RIR database for the space.1 of 636
AS-SET: not foundAS136948:AS-APPeeringDB names AS136948:AS-AP; no IRR database read has it.

Route objects not announced

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

103.99.248.0/22APNICValid
103.99.248.0/23APNICValid
103.99.250.0/23APNICValid

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.