bgpreport

Network · data from 2026-11-12

AS147226 FUTURE CONNECT BROADBAND

Registry name: FUTURE01-AS-IN - FUTURE CONNECT BROADBANDPRIVATE LIMITED, IN · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS147226, 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.
2400:3be0:1a00::/40 Invalid: maxLength Nonecovered by 2400:3be0::/32 16 3%low visibility 9
2400:3be0:1b00::/40 Invalid: maxLength Nonecovered by 2400:3be0::/32 16 3%low visibility 9
103.170.228.0/23 Valid RIR databaseAPNIC 671 100% 67
103.177.182.0/23 Valid RIR databaseAPNIC 671 100% 67
2400:3be0::/32 Valid RIR databaseAPNIC 635 100% 67
2400:3be0::/48 Valid RIR databaseAPNIC 635 100% 67
2400:3be0:182::/48 Valid RIR databaseAPNIC 635 100% 67
2400:3be0:183::/48 Valid RIR databaseAPNIC 635 100% 67
2400:3be0:228::/48 Valid RIR databaseAPNIC 635 100% 67
2400:3be0:229::/48 Valid RIR databaseAPNIC 635 100% 67
2400:3be0:2000::/48 Valid RIR databaseAPNIC 635 100% 67
2400:3be0:3000::/48 Valid RIR databaseAPNIC 635 100% 67
2400:3be0:4000::/48 Valid RIR databaseAPNIC 635 100% 67
2400:3be0:8000::/48 Valid RIR databaseAPNIC 635 100% 67
2400:3be0:9000::/48 Valid RIR databaseAPNIC 635 100% 67
2400:3be0:1000::/48 Valid RIR databaseAPNIC 634 100% 67
2400:3be0:5000::/48 Valid RIR databaseAPNIC 634 100% 67
2400:3be0:6000::/48 Valid RIR databaseAPNIC 634 100% 67
2400:3be0:7000::/48 Valid RIR databaseAPNIC 634 100% 67
103.170.228.0/24 Valid RIR databaseAPNIC 35 5%low visibility 27
103.170.229.0/24 Valid RIR databaseAPNIC 35 5%low visibility 27
103.177.182.0/24 Valid RIR databaseAPNIC 35 5%low visibility 27
103.177.183.0/24 Valid RIR databaseAPNIC 35 5%low visibility 27

AS-SET

PeeringDB's irr_as_set for AS147226: AS147226:AS-FCBIND. 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 (AS147226 isn't in the set, or no route object for AS147226 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 objectsAS147226 in itNot covered
AS147226:AS-FCBIND APNIC 2128 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 5 are in fix.csv.

  • ROA: maxLength2
  • Route object: none2
  • Route object: not announced1
ChangePrefix or setDetailFull-table peers
ROA: maxLength2400:3be0:1a00::/40ROA 2400:3be0::/32 AS147226 has maxLength 32; the route is a /40. Raise the maxLength, or add a ROA for 2400:3be0:1a00::/40.16 of 636
Route object: none2400:3be0:1a00::/40No route object for it. A route object for 2400:3be0::/32 with origin AS147226 covers it (filters allowing more-specifics accept it). Add a route object with origin AS147226 in the RIR database for the space.16 of 636
ROA: maxLength2400:3be0:1b00::/40ROA 2400:3be0::/32 AS147226 has maxLength 32; the route is a /40. Raise the maxLength, or add a ROA for 2400:3be0:1b00::/40.16 of 636
Route object: none2400:3be0:1b00::/40No route object for it. A route object for 2400:3be0::/32 with origin AS147226 covers it (filters allowing more-specifics accept it). Add a route object with origin AS147226 in the RIR database for the space.16 of 636

Route objects not announced

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

2407:b940::/32APNICValid

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.