bgpreport

Network · data from 2026-11-12

AS269862 FASTNET Internet

Registry name: AS269862 - M & B Soluciones Peru S.A.C. (FASTNET), PE · PeeringDB

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

Announced routes

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

38.56.104.0/24 No ROA Nonecovered by 38.56.96.0/20 24 4%low visibility 11
38.56.110.0/24 No ROA Other IRR onlyRADB 24 4%low visibility 11
138.185.14.0/24 Valid Other IRR onlyRADB 672 100% 66
45.189.188.0/24 Valid Other IRR onlyRADB 668 99% 67
2803:b0e0:7100::/48 Valid Other IRR onlyRADB 636 100% 67
2803:b0e0:2698::/48 Valid Other IRR onlyRADB 635 100% 69
2803:b0e0:26a0::/48 Valid Other IRR onlyRADB 635 100% 69
2803:b0e0:26a1::/48 Valid Other IRR onlyRADB 635 100% 69
2803:b0e0:99c0::/48 Valid Other IRR onlyRADB 635 100% 69
201.218.156.0/24 Valid RIR databaseLACNIC, RADB 672 100% 67
38.137.196.0/24 Valid RIR databaseARIN, RADB 671 100% 66
38.199.94.0/24 Valid RIR databaseARIN, RADB 671 100% 67
38.199.95.0/24 Valid RIR databaseARIN, RADB 671 100% 67
201.218.150.0/24 Valid RIR databaseLACNIC, RADB 671 100% 66
38.56.111.0/24 Valid RIR databaseARIN, RADB 670 100% 67

AS-SET

PeeringDB's irr_as_set for AS269862: AS-FASTNETPERU. 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 (AS269862 isn't in the set, or no route object for AS269862 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 objectsAS269862 in itNot covered
AS-FASTNETPERU RADB 161212 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 35 are in fix.csv.

  • ROA: none2
  • Route object: none1
  • Route object: RIR8
  • Route object: not announced24
ChangePrefix or setDetailFull-table peers
ROA: none38.56.104.0/24No ROA covers it. Add a ROA for AS269862, maxLength 24.24 of 673
Route object: none38.56.104.0/24No route object for it. A route object for 38.56.96.0/20 with origin AS269862 covers it (filters allowing more-specifics accept it). Add a route object with origin AS269862 in the RIR database for the space.24 of 673
ROA: none38.56.110.0/24No ROA covers it. Add a ROA for AS269862, maxLength 24.24 of 673
Route object: RIR38.56.110.0/24Route object only in RADB. Add it in the RIR database for the space.24 of 673
Route object: RIR138.185.14.0/24Route object only in RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR45.189.188.0/24Route object only in RADB. Add it in the RIR database for the space.668 of 673
Route object: RIR2803:b0e0:7100::/48Route object only in RADB. Add it in the RIR database for the space.636 of 636
Route object: RIR2803:b0e0:2698::/48Route object only in RADB. Add it in the RIR database for the space.635 of 636
Route object: RIR2803:b0e0:26a0::/48Route object only in RADB. Add it in the RIR database for the space.635 of 636
Route object: RIR2803:b0e0:26a1::/48Route object only in RADB. Add it in the RIR database for the space.635 of 636
Route object: RIR2803:b0e0:99c0::/48Route object only in RADB. Add it in the RIR database for the space.635 of 636

Route objects not announced

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

38.56.96.0/19RADBNo ROA
38.56.96.0/20RADBNo ROA
38.56.112.0/20RADBNo ROA
38.137.192.0/20RADBNo ROA
38.137.208.0/20RADBNo ROA
38.137.221.0/24RADBNo ROA
38.195.94.0/24RADBNo ROA
45.189.188.0/22LACNIC, RADBValid
45.189.190.0/24RADBValid
45.189.191.0/24RADBValid
138.99.178.0/24LACNICValid
138.99.179.0/24LACNIC, RADBValid
168.194.168.0/24RADBValid
170.82.224.0/24LACNICValid
201.218.130.0/24LACNIC, RADBValid
201.218.146.0/24LACNIC, RADBValid
201.218.158.0/24LACNICValid
2803:b0e0::/32LACNIC, RADBValid
2803:b0e0:8021::/48LACNIC, RADBValid
2803:b0e0:9983::/48LACNIC, RADBValid
2803:b0e0:9984::/48LACNIC, RADBValid
2803:b0e0:9989::/48LACNIC, RADBValid
2803:b0e0:998a::/48RADBValid
2803:b0e0:9992::/48RADBValid

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.