bgpreport

Network · data from 2026-11-12

AS267387 FLASH NETWORK INTERNET LTDA

Registry name: AS267387 - FLASH NETWORK INTERNET LTDA, BR · PeeringDB

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

Announced routes

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

45.234.246.0/24 No ROA Other IRR onlyRADB 669 99% 67
2804:4cb8:7000::/36 No ROA Other IRR onlyRADB 635 100% 69
2804:4cb8::/32 No ROA Other IRR onlyRADB 1 0%low visibility 1
45.234.244.0/23 Valid Other IRR onlyRADB, TC 672 100% 67
45.234.247.0/24 Valid Other IRR onlyRADB, TC 671 100% 67
2804:4cb8::/35 Valid Other IRR onlyTC 636 100% 69
2804:4cb8:4000::/36 Valid Other IRR onlyTC 636 100% 69
2804:4cb8:5000::/36 Valid Other IRR onlyTC 636 100% 69
2804:4cb8:6000::/36 Valid Other IRR onlyTC 636 100% 69
2804:4cb8:8000::/33 Valid Other IRR onlyRADB, TC 636 100% 69
45.234.244.0/24 Valid Other IRR onlyTC 124 18% 44
45.234.245.0/24 Valid Other IRR onlyTC 124 18% 44
2804:4cb8::/36 Valid Other IRR onlyTC 113 18% 43
2804:4cb8:1000::/36 Valid Other IRR onlyTC 113 18% 43
2804:4cb8:4000::/37 Valid Other IRR onlyTC 113 18% 43
2804:4cb8:4800::/37 Valid Other IRR onlyTC 113 18% 43
2804:4cb8:5000::/37 Valid Other IRR onlyTC 113 18% 43
2804:4cb8:5800::/37 Valid Other IRR onlyTC 113 18% 43
2804:4cb8:6000::/37 Valid Other IRR onlyTC 113 18% 43
2804:4cb8:6800::/37 Valid Other IRR onlyTC 113 18% 43
2804:4cb8:8000::/34 Valid Other IRR onlyTC 113 18% 43
2804:4cb8:c000::/34 Valid Other IRR onlyTC 113 18% 43

AS-SET

PeeringDB's irr_as_set for AS267387: TC::AS267387:AS-ANNOUNCEMENTS. 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 (AS267387 isn't in the set, or no route object for AS267387 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 objectsAS267387 in itNot covered
TC::AS267387:AS-ANNOUNCEMENTS TC 1125 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 28 are in fix.csv.

  • ROA: none3
  • Route object: RIR22
  • Route object: not announced3
ChangePrefix or setDetailFull-table peers
ROA: none45.234.246.0/24No ROA covers it. Add a ROA for AS267387, maxLength 24.669 of 673
Route object: RIR45.234.246.0/24Route object only in RADB. Add it in the RIR database for the space.669 of 673
ROA: none2804:4cb8:7000::/36No ROA covers it. Add a ROA for AS267387, maxLength 36.635 of 636
Route object: RIR2804:4cb8:7000::/36Route object only in RADB. Add it in the RIR database for the space.635 of 636
ROA: none2804:4cb8::/32No ROA covers it. Add a ROA for AS267387, maxLength 32.1 of 636
Route object: RIR2804:4cb8::/32Route object only in RADB. Add it in the RIR database for the space.1 of 636
Route object: RIR45.234.244.0/23Route object only in RADB, TC. Add it in the RIR database for the space.672 of 673
Route object: RIR45.234.247.0/24Route object only in RADB, TC. Add it in the RIR database for the space.671 of 673
Route object: RIR2804:4cb8::/35Route object only in TC. Add it in the RIR database for the space.636 of 636
Route object: RIR2804:4cb8:4000::/36Route object only in TC. Add it in the RIR database for the space.636 of 636
Route object: RIR2804:4cb8:5000::/36Route object only in TC. Add it in the RIR database for the space.636 of 636
Route object: RIR2804:4cb8:6000::/36Route object only in TC. Add it in the RIR database for the space.636 of 636
Route object: RIR2804:4cb8:8000::/33Route object only in RADB, TC. Add it in the RIR database for the space.636 of 636
Route object: RIR45.234.244.0/24Route object only in TC. Add it in the RIR database for the space.124 of 673
Route object: RIR45.234.245.0/24Route object only in TC. Add it in the RIR database for the space.124 of 673
Route object: RIR2804:4cb8::/36Route object only in TC. Add it in the RIR database for the space.113 of 636
Route object: RIR2804:4cb8:1000::/36Route object only in TC. Add it in the RIR database for the space.113 of 636
Route object: RIR2804:4cb8:4000::/37Route object only in TC. Add it in the RIR database for the space.113 of 636
Route object: RIR2804:4cb8:4800::/37Route object only in TC. Add it in the RIR database for the space.113 of 636
Route object: RIR2804:4cb8:5000::/37Route object only in TC. Add it in the RIR database for the space.113 of 636
Route object: RIR2804:4cb8:5800::/37Route object only in TC. Add it in the RIR database for the space.113 of 636
Route object: RIR2804:4cb8:6000::/37Route object only in TC. Add it in the RIR database for the space.113 of 636
Route object: RIR2804:4cb8:6800::/37Route object only in TC. Add it in the RIR database for the space.113 of 636
Route object: RIR2804:4cb8:8000::/34Route object only in TC. Add it in the RIR database for the space.113 of 636
Route object: RIR2804:4cb8:c000::/34Route object only in TC. Add it in the RIR database for the space.113 of 636

Route objects not announced

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

45.234.244.0/22RADBNo ROA
45.234.246.0/23RADBNo ROA
2804:4cb8::/33RADBNo ROA

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.