Short answer: paste the data, pick the format, copy the table. Values are escaped so a pipe or a line break cannot break the grid, and a ragged row is an error with a row number rather than a silently shifted column.
Why the parser matters
Splitting on commas looks fine until a field is "Smith, J" or contains a newline, at which point the table is quietly wrong. This page reuses the RFC 4180 parser from the CSV converter: quoted fields, doubled quotes inside quotes, and line breaks inside quotes all behave, and an unterminated quote is reported instead of merging the rest of the file into one cell.
Reading the output
The first row is the header, the second is the alignment row, and everything after that is data. The padding is cosmetic, but it keeps the raw Markdown readable in a diff — which is the whole reason to generate the table instead of typing it.
Need the same data as JSON for a script? Use the CSV converter. If the numbers came out of a subnet calculation, theCIDR calculator is where they came from.